C:\Users\<Username>\.aws\credentialsHere's a link to the documentation:
[default] aws_access_key_id=xxx aws_secret_access_key=xxx [abc] aws_access_key_id=xxx aws_secret_access_key=xxx aws_session_token="xxx"
Thanks for this suggestion too. We will see what other users prefer.The AWS CLI stores user credentials in a file and it would be ideal if that same file could be used to authenticate to S3 in WinSCP.
/script=script.txt)? Even with credentials in the environment, I still get prompted for access key and secret. Ideally this would also support searching for credentials in the order:
Imo, the current behaviour goes better with the GUI interface.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:
UseIs 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
It's long time, since I've made the decision. But I believe it was the size and the dependencies.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?
You can post new topics in this forum