Editing AWS Instance Metadata Service (IMDS)
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
If you use [[Auto Scaling groups]] and you need to require the use of IMDSv2 on all new instances, your Auto Scaling groups must use [[launch templates]]. | If you use [[Auto Scaling groups]] and you need to require the use of IMDSv2 on all new instances, your Auto Scaling groups must use [[launch templates]]. | ||
− | |||
− | |||
− | |||
− | |||
== Related == | == Related == | ||
Line 16: | Line 12: | ||
* <code>[[ec2-imdsv2-check]]</code>, the rule is <code>[[NON_COMPLIANT]]</code> if the <code>[[HttpTokens]]</code> is set to optional. | * <code>[[ec2-imdsv2-check]]</code>, the rule is <code>[[NON_COMPLIANT]]</code> if the <code>[[HttpTokens]]</code> is set to optional. | ||
* <code>[[aws ec2 describe-instances]] | grep [[HttpTokens]]</code> | * <code>[[aws ec2 describe-instances]] | grep [[HttpTokens]]</code> | ||
− | * [[AWS | + | * [[Datadog AWS Integration Billing]] |
− | |||
− | |||
− | |||
== See also == | == See also == |
Advertising: