-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Support setting EC2 instance metadata to require token (IMDSv2) #10949
Comments
This should also support optionally setting the PUT response hop limit Such as outlined by the following AWS CLI command resource "aws_instance" "this" {
// ...
metadata_options {
http_tokens = "required"
http_put_response_hop_limit = "1"
}
} |
Support for configuring metadata options in the |
This has been released in version 2.55.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
Launched here: https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/
EC2 instances can be set to require IMDSv2 only. This can be done to running instances with https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#EC2.ModifyInstanceMetadataOptions or new instances with the
MetadataOptions
field ofRunInstancesInput
.New or Affected Resource(s)
aws_instance
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: