Skip to content
Discussion options

You must be logged in to vote

Hi @lajos-resnweb,

Sorry to hear about the issues caused by the fallback. If you are using version 3.286.0 and up, you'll be able to disable the V1 fallback using the AWS_EC2_METADATA_V1_DISABLED env var, OR using the ec2_metadata_v1_disabled configuration either in the shared config file or in code by passing it into an instance of InstanceProfileProvider as a config option when setting the credentials configuration option on an AWS service client.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@lajos-resnweb
Comment options

Answer selected by stobrien89
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants