-
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
Document the AWS_EC2_METADATA_DISABLED environment variable #5623
Comments
Today our CI deploys in Github Actions started fail on AWS CLI commands (
and exit with 255 code. No other error messages. Setting Posting this here since googling this brought me here and it might help others too. |
* add env variable aws/aws-cli#5623 (comment) * set environment variables in env node * Update s3-prod.yml
Hi all, this is now in the documentation of environment variables for the CLI: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html |
|
The v2 AWS cli throws an exception if run on Azure, e.g. via Github Actions due to presumeabley due to the metadata service using the same IP address. Apparently handling exceptions is too difficult for AWS. aws/aws-cli#5262 aws/aws-cli#5623
The v2 AWS cli throws an exception if run on Azure, e.g. via Github Actions due to presumeabley due to the metadata service using the same IP address. Apparently handling exceptions is too difficult for AWS. aws/aws-cli#5262 aws/aws-cli#5623
This should solve the recent mysterious publication failure.
Fixed bug nspcc-dev/neofs-s3-gw#798 This bug is only reproducible on ubuntu-latest in github actions. This is a bug specifically of github acions, not the neofs-s3-gw: actions/runner-images#2791 aws/aws-cli#5623 Signed-off-by: Oleg Kulachenko <[email protected]>
Fixed bug nspcc-dev/neofs-s3-gw#798 This bug is only reproducible on ubuntu-latest in github actions. This is a bug specifically of github acions, not the neofs-s3-gw: actions/runner-images#2791 aws/aws-cli#5623 Signed-off-by: Oleg Kulachenko <[email protected]>
Fixed bug nspcc-dev/neofs-s3-gw#798 This is a test environment error, not neofs-s3-gw: actions/runner-images#2791 aws/aws-cli#5623 Signed-off-by: Oleg Kulachenko <[email protected]>
Fixed bug nspcc-dev/neofs-s3-gw#798 This is a test environment error, not neofs-s3-gw: actions/runner-images#2791 aws/aws-cli#5623 Tests results: https://github.com/vvarg229/neofs-node/actions/runs/5601200752/jobs/10244709153 https://http.t5.fs.neo.org/86C4P6uJC7gb5n3KkwEGpXRfdczubXyRNW5N9KeJRW73/216-1689781099/index.html#
Fixed bug nspcc-dev/neofs-s3-gw#798 This is a test environment error, not neofs-s3-gw: actions/runner-images#2791 aws/aws-cli#5623 Signed-off-by: Oleg Kulachenko <[email protected]>
Is your feature request related to a problem? Please describe.
If no region is set, the AWS CLI tries to use the IMDS service to determine it. In some cases, like when running the AWS CLI on an Azure instance, another service can be running at the same non-routable IP address used by IMDS. One way to get around this is to explicitly set a region. However, there is an undocumented environment variable that can prevent the request to IMDS:
Related issues:
Describe the solution you'd like
Document the environment variable in the user guide:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html
Describe alternatives you've considered
Setting the region can prevent this behavior, but using the environment variable is more explicit in controlling it.
Additional context
None
The text was updated successfully, but these errors were encountered: