$AWS_PROFILE is not honored

[matt-pilgrim]

This mentions something similar, and suggests using --configure, but that apparently uses the ~/.s3cfg file. Shouldn't I be able to use a command like AWS_PROFILE=foo s3cmd ... and use the "foo" profile from ~/.aws/credentials?

As someone who routinely uses multiple aws profiles, this is painful because I don't really want to keep another file in sync, and I also don't want to have to view my credentials files and copy/paste environment variables for AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY.

If there is agreement that this is a bug, I can probably submit a patch.

EDIT: found this comment from 2015 suggesting using the credentials file, and this mention in the same thread that a patch would be accepted. Can anyone confirm this is still desired?

[AnthonyWC]

+1 I was going to submit the same issue.

[felipe1982]

If like this feature. I'm using awsume in the meantime which creates environment variables

Sent from my Google Pixel using FastHub

[alexanderkjeldaas]

@felipe1982 which awsume command do you use? awsume doesn't set any environment variables for me.

[felipe1982]

That's only what awsume does: sets environment variables. Make sure you have the Alias set, or run . awsume

[fviard]

Should be already fixed with merged PR #966 .