The current implementation requires to check the box: "Read credentials from AWS CLI configuration". I wonder if that is needed? I nicer user experience would be to search for the credentials in the order:
Imo, the current behaviour goes better with the GUI interface.
Let's see what others think.
Is there a way to use this feature in the automation interface (
/script=script.txt)? Even with credentials in the environment, I still get prompted for access key and secret.
S3CredentialsEnvraw session settings:
open s3://s3.amazonaws.com/ -rawsettings S3CredentialsEnv=on
Just for my curiosity, may I ask why you are using a fork of libs3 over the official AWS SDK? The license? Or the size?
It's long time, since I've made the decision. But I believe it was the size and the dependencies.