-
Notifications
You must be signed in to change notification settings - Fork 4k
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
awscli 1.16.285 changed how to find credentials on EC2 endpoint #4682
Comments
Ditto, this narrowly missed breaking our production environment because we missed locking the aws-cli version to a specific minor revision. Major regression. Good diagnostics @scottschreckengaust |
Same, our cli version updated with our pre-deployment for production and we caught it... seeing the same thing. AWS cli installed in docker image is not able to get credentials on EC2 within ECS. |
We luckily caught this in our pipelines (the ones that aren't pinned to a specific version) but this is a huge issue. |
Same. This needs to be reverted. |
Thanks for bringing this to our attention. We'll be reverting this ASAP and cutting an additional release today. |
AWS CLI v1.16.286 has been released and reverts to the previous behavior fixing the regression. We are still working on a proper fix to support the new IMDS behavior. |
The meta data endpoint seems to have changed from
/latest/meta-data/iam/security-credentials/
->/latest/api/token
and can no longer get an EC2 instance role.The below are snippets from a
aws s3 ls --debug
command running within a docker (Docker version 19.03.4, build 9013bf583a) on ubuntu "Ubuntu 16.04.6 LTS" EC2 instance:The text was updated successfully, but these errors were encountered: