Editing AWS Instance Metadata Service (IMDS)

* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html


* [[Instance metadata and user data]]

* [[Azure Instance Metadata Service]]

* [[IMDSv2]]

== See also ==
* {{AWS}}

[[Category:AWS]]
@@ Line 2: / Line 2: @@
-* <code>[[aws ec2 modify-instance-metadata-options]]</code>
+* [[Instance metadata and user data]]
-* [[IMDSv2]]
-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]].
+* [[Azure Instance Metadata Service]]
-* [[Datadog AWS Integration Billing]]: If your EC2 instances are configured to require the use of Instance Metadata Service Version 2 (IMDSv2), then you must set the parameter ec2_prefer_imdsv2 to true in your Datadog agent configuration to avoid double-billing.
+* [[IMDSv2]]
-  TOKEN=`[[curl -X PUT]] "http://169.254.169.254/latest/api/token" [[-H]] "X-aws-ec2-metadata-token-ttl-seconds: 21600"` \ && [[curl -H]] "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/[[user-data]]
-== Related ==
-* [[Azure Instance Metadata Service]]
-* [[Instance metadata and user data]]
-* <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>
-* [[AWS EC2 Instance Connect]]
-* [[Datadog]]: <code>[[DD_EC2_PREFER_IMDSV2]]</code>
-* [[IMDS initiate session]]
-* <code>[[Failed to refresh cached credentials, no EC2 IMDS role found]]</code>
 == See also ==
-* {{IMDS}}
+* {{AWS}}
-* {{AWS EC2}}
 [[Category:AWS]]