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.
I'm not sure how to create that setup on AWS but you can read more from the above saml2aws project page.
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.
Add patch
None
None
None
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
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.