Problem/Motivation

We are using https://github.com/Versent/saml2aws to access AWS locally. All other options are disabled due to security. Because we have errors in AWS and they are impossible to debug on server then having dummy connection is not enough.

Steps to reproduce

I'm not sure how to create that setup on AWS but you can read more from the above saml2aws project page.

Proposed resolution

We don't actually need more than just add 'profile' key to options because aws sdk supports it. Then aws sdk will go and read ~/.aws/credentials file and allow connection - just like key and secret would.

Remaining tasks

Add patch

User interface changes

None

API changes

None

Data model changes

None

CommentFileSizeAuthor
#2 flysystem_s3-Allow-authentication-with-profile-3184530-2.patch1.28 KBhkirsman

Comments

hkirsman created an issue. See original summary.

hkirsman’s picture

hkirsman commented
StatusFileSize
new flysystem_s3-Allow-authentication-with-profile-3184530-2.patch1.28 KB

Adding patch

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Active » Reviewed & tested by the community

Thanks for the patch! Can confirm that this works. I think it's quite neat to not have to specify the key and secret, in particular, in settings.php directly, but just reference the profile and have the credentials in ~/.aws/credentials.