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

[v15] Re-enable AWS IMDSv1 fallback #39366

Merged
merged 1 commit into from Mar 14, 2024

Conversation

reedloden
Copy link
Contributor

Backport #39363 to branch/v15

changelog: Re-enable AWS IMDSv1 fallback due to some EKS clusters having their IMDSv2 hop limit set to 1, leading to IMDSv2 requests failing. Users who wish to keep IMDSv1 fallback disabled can set the AWS_EC2_METADATA_V1_DISABLED environmental variable.

It was discovered that some customers' EKS clusters did not have their IMDSv2 hop limits
set correctly, causing requests for key functionality to attempt IMDSv1 fallback and failing.

For now, re-enable IMDSv1 fallback by way of removing the explicit disabling of
`EC2MetadataEnableFallback` until better documentation, error handling, and other work
can be done to inform customers that they need to correctly set their IMDSv2 hop limits.
@reedloden reedloden self-assigned this Mar 14, 2024
@github-actions github-actions bot added application-access audit-log Issues related to Teleports Audit Log backport size/sm labels Mar 14, 2024
@reedloden reedloden added this pull request to the merge queue Mar 14, 2024
Merged via the queue into branch/v15 with commit 0069a3d Mar 14, 2024
34 checks passed
@reedloden reedloden deleted the bot/backport-39363-branch/v15 branch March 14, 2024 19:49
@r0mant r0mant mentioned this pull request Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application-access audit-log Issues related to Teleports Audit Log backport size/sm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants