-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS_PROFILE is ignored when AWS_ROLE_ARN is set #8883
Comments
Thanks for reaching out. I'm not able to reproduce this, when I set Also the documentation for assuming a role with web identity notes for environment variables
For further investigation, could you provide your debug logs (with any sensitive info redacted) by adding |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
I face this issue when I use
Setting |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Issue persists in version |
If you add |
Describe the bug
when using the environment variable
AWS_PROFILE
, if theAWS_ROLE_ARN
env exists the profile env is ignored.but when using the
--profile
the new profile is used.Expected Behavior
AWS_PROFILE should not get override
Current Behavior
AWS_PROFILE
env is ignored ifAWS_ROLE_ARN
is setReproduction Steps
run aws configure
run aws sts get-caller-identity
Possible Solution
No response
Additional Information/Context
No response
CLI version used
aws-cli/2.17.33 Python/3.11.9 Linux/5.10.219-208.866.amzn2.x86_64 exe/x86_64.debian.11
Environment details (OS name and version, etc.)
docker image python:3.11-slim-bullseye
The text was updated successfully, but these errors were encountered: