Skip to content
This repository has been archived by the owner on Jul 20, 2024. It is now read-only.

Security/Compliance fix - require IMDSv2 on NAT instance (#48) #55

Merged
merged 1 commit into from
Nov 24, 2022
Merged

Security/Compliance fix - require IMDSv2 on NAT instance (#48) #55

merged 1 commit into from
Nov 24, 2022

Conversation

mackenzie-oa
Copy link
Contributor

Follow security best practices by disabling IMDSv1 on the Launch Template.

This will help anyone using this module who is required to meet compliance and/or security requirements that flag this feature.

https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/
https://aquasecurity.github.io/tfsec/v1.8.0/checks/aws/autoscaling/enforce-http-token-imds/

Follow security best practices by disabling IMDSv1 on the Launch
Template.

This will help anyone using this module who is required to meet compliance
and/or security requirements that flag this feature.

https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/
https://aquasecurity.github.io/tfsec/v1.8.0/checks/aws/autoscaling/enforce-http-token-imds/
@int128 int128 merged commit 1c8ffeb into int128:master Nov 24, 2022
@mackenzie-oa
Copy link
Contributor Author

Perfect, can you bump the terraform module version so I can use the terraform registry? Thanks again for merging my PR @int128 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants