chore(cloudformation): Only allow IMDSv2 on Gateway instances #2934
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
coldlink
approved these changes
Oct 14, 2024
coldlink
requested review from
guardian-ci
and removed request for
guardian-ci
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
As per https://docs.aws.amazon.com/securityhub/latest/userguide/ec2-controls.html#ec2-8 we should not be allowing access to IMDSv1 anymore.
This resolves 4 HIGH FSBP vulnerabilities.
How to test
Check Cloudwatch metrics for any usage of
MetadataNoToken, if no usage then it is safe for us to disable IMDSv1.