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

NodeGroup IMDSv2 support #821

Closed
ryneal opened this issue Sep 6, 2021 · 2 comments
Closed

NodeGroup IMDSv2 support #821

ryneal opened this issue Sep 6, 2021 · 2 comments
Labels

Comments

@ryneal
Copy link

ryneal commented Sep 6, 2021

What problem are you facing?

It is not possible to set IMDSv2 for EC2 instances created by NodeGroup, it currently defaults to IMDSv1.

How could Crossplane help solve your problem?

Requesting parameters added to CRD to configure IMDSv2 on NodeGroup EC2 instances.

@ryneal ryneal added the enhancement New feature or request label Sep 6, 2021
@chlunde
Copy link
Collaborator

chlunde commented Oct 5, 2021

I think this requires launch templates, which is this issue: #338
It should be possible to implement this now since AWS SDK for Go v2 has been updated.

LaunchTemplateData.MetadataOptions.HttpTokens -> required
LaunchTemplateData.MetadataOptions.HttpPutResponseHopLimit -> 1

@github-actions
Copy link

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Sep 18, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants