Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    Interesting, but it still sets the profile to foo, so it works for you anyway? Commented May 8, 2018 at 11:35
  • I opened an issue with the developers. Seems AWS_PROFILE is ignored if AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID are set. github.com/aws/aws-cli/issues/3304 Commented May 9, 2018 at 9:45
  • 1
    Mine is working now :) I doublechecked my variables and I only set my variable as a shell variable and not as an environment variable. When I did that it started working Commented May 9, 2018 at 10:48
  • 2
    Still not working for me, with either Env of Shell vars. Could you provide any more detail or examples? Commented May 16, 2018 at 11:26
  • I didn't do much. I am using fish so I type: "set -xg AWS_PROFILE myprofile". Optionally use -U as well to set it everywhere. Then "env" displays the variable and aws configure list works as expected Commented May 23, 2018 at 8:51