Skip to content
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

[BUG] AWS Metdata fails when IMDSv2 is enabled #65513

Closed
garethgreenaway opened this issue Nov 3, 2023 · 1 comment · Fixed by #65512
Closed

[BUG] AWS Metdata fails when IMDSv2 is enabled #65513

garethgreenaway opened this issue Nov 3, 2023 · 1 comment · Fixed by #65512
Assignees
Labels
Bug broken, incorrect, or confusing behavior Chlorine v3007.0 Duplicate Duplicate of another issue or PR - will be closed

Comments

@garethgreenaway
Copy link
Contributor

Description
If an AWS instance is running in an environment where IMDSv2 is enabled then the metadata grain will fail with a 401 Unauthorized error.

Setup
Create an instance in an AWS environment where IMDSv2 is enabled. On that instance enable the metadata_server_grains grain in the minion configuration.

Steps to Reproduce the behavior
Query the grains on the running instance.

Expected behavior
AWS Metadata grains should be returned.

@garethgreenaway garethgreenaway added Bug broken, incorrect, or confusing behavior needs-triage labels Nov 3, 2023
@garethgreenaway garethgreenaway self-assigned this Nov 3, 2023
@garethgreenaway garethgreenaway added this to the Chlorine v3007.0 milestone Nov 3, 2023
@OrangeDog
Copy link
Contributor

Duplicate of #65233
See also #60668

@OrangeDog OrangeDog added the Duplicate Duplicate of another issue or PR - will be closed label Nov 4, 2023
@garethgreenaway garethgreenaway linked a pull request Nov 6, 2023 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Chlorine v3007.0 Duplicate Duplicate of another issue or PR - will be closed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants