-
Notifications
You must be signed in to change notification settings - Fork 1.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
Getting "botocore.exceptions.NoCredentialsError: Unable to locate credentials" on ec2 instance as of botocore-1.13.21 #1897
Comments
I'm experiencing similar. When creating a boto3 client on an EKS node I get the following boto3 logging output: ` During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): The IMDSv2 metadata token service on this node does not appear functional. The following request just hangs: botocore==1.13.19 however does work in this environment, presumably using IMDSv1 (which is functional in this env. |
This has been confirmed and has been fixed as of 1.13.22. |
Ah yes my mistake, I didn't think to look in the closed issues. |
It seems like as of botocore-1.13.21, using boto3 on my ec2 instances is failing with
botocore.exceptions.NoCredentialsError: Unable to locate credentials
where it was working perfectly fine beforehand.The code itself is pretty simple:
The text was updated successfully, but these errors were encountered: