Difference between revisions of "AWS Instance Metadata Service (IMDS)"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
* [[Azure Instance Metadata Service]] | * [[Azure Instance Metadata Service]] | ||
* [[Instance metadata and user data]] | * [[Instance metadata and user data]] | ||
| − | * <code>[[ec2-imdsv2-check]]</code>, the rule is [[NON_COMPLIANT]] if the [[HttpTokens]] 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. |
== See also == | == See also == | ||
Revision as of 13:19, 4 October 2022
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
- Azure Instance Metadata Service
- Instance metadata and user data
ec2-imdsv2-check, the rule isNON_COMPLIANTif theHttpTokensis set to optional.
See also
- IMDS, IMDS versions (IMDSv2), IMDS initiate session,
ec2-imdsv2-check, aws ec2 modify-instance-metadata-options, /latest/meta-data, /latest/user-data, modify-instance-metadata-defaults - AWS EC2, Amazon EC2 API,
aws ec2, AWS::EC2, Amazon EC2 Spot Instances, CPU credits, Instance type, EC2 limitations, 169.254.169.254, Instance metadata and user data (IMDS),InstanceType, InstanceId, Amazon EC2 Auto Scaling, AWS EC2 Instance Connect, launch template, lifecycle, AWS Security group (SG), Amazon EC2 Recycle Bin, Amazon EC2 Mac Instances, Global View
Advertising:
