AWS Security ChangesHomeSearch

AWS AWSEC2: Document ImdsV1Enabled metric for tracking IMDSv1 usage

Service: AWSEC2 · 2026-10-23 · Documentation medium

File: AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.md · Type: ssrf

Summary

Adds documentation for a new CloudWatch metric, ImdsV1Enabled, that reports whether an instance is configured to allow IMDSv1 (httpTokens = optional) versus required. Updates the metric count from two to three, explains that the metric is published based on instance configuration (independent of IMDS calls), and describes using it to find instances still allowing IMDSv1 across accounts and Regions during IMDSv2 migration.

Security assessment

IMDSv1 exposure is a known SSRF credential-theft vector; this change documents a monitoring metric that lets operators find instances still configured to allow IMDSv1 even when no IMDSv1 calls occur, supporting identification and remediation. It is guidance/monitoring documentation for an existing configuration state, not a fix for a named vulnerability or incident, so security_issue_related is false.

Evidence

+`ImdsV1Enabled` – This metric indicates whether an instance is configured to allow IMDSv1. A value of `1` indicates that IMDSv1 is enabled (`httpTokens = optional`). A value of `0` indicates that IMDSv1 is disabled (`httpTokens = required`).

Diff

diff --git a/AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.md b/AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.md
index 1784792..e6e0f1a 100644
--- a//AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.md
+++ b//AWSEC2/latest/UserGuide/instance-metadata-transition-to-version-2.md
@@ -41 +41 @@ IMDS Packet Analyzer is an open-source tool that identifies and logs IMDSv1 call
-CloudWatch provides the following two metrics for monitoring your instances:
+CloudWatch provides the following three metrics for monitoring your instances:
@@ -47 +47,5 @@ CloudWatch provides the following two metrics for monitoring your instances:
-For each EC2 instance, these metrics are mutually exclusive. When IMDSv1 is enabled (`httpTokens = optional`), only `MetadataNoToken` emits. When IMDSv1 is disabled (`httpTokens = required`), only `MetadataNoTokenRejected` emits. For when to use these metrics, see Recommended path to requiring IMDSv2.
+`ImdsV1Enabled` – This metric indicates whether an instance is configured to allow IMDSv1. A value of `1` indicates that IMDSv1 is enabled (`httpTokens = optional`). A value of `0` indicates that IMDSv1 is disabled (`httpTokens = required`).
+
+The `MetadataNoToken` and `MetadataNoTokenRejected` metrics emit only when the IMDS is accessed. In contrast, Amazon EC2 publishes the `ImdsV1Enabled` metric based on the instance's configuration. As a result, you can identify instances that still allow IMDSv1 across your accounts and Regions, even when no IMDSv1 calls are being made.
+
+For each EC2 instance, the `MetadataNoToken` and `MetadataNoTokenRejected` metrics are mutually exclusive. When IMDSv1 is enabled (`httpTokens = optional`), only `MetadataNoToken` emits. When IMDSv1 is disabled (`httpTokens = required`), only `MetadataNoTokenRejected` emits. For when to use these metrics, see Recommended path to requiring IMDSv2.
@@ -147,0 +152,2 @@ To assess your IMDSv2 migration scope, identify instances that are configured to
+To see how many instances in an account and Region still allow IMDSv1, use the `ImdsV1Enabled` CloudWatch metric. This metric is published for each instance based on its configuration, so the Sum of the metric is the number of instances that still allow IMDSv1, even when no IMDSv1 calls are being made. Track it across your accounts and Regions to measure your migration progress. Then, to identify which specific instances still allow IMDSv1, use the Amazon EC2 console or the AWS CLI. For a description of the `ImdsV1Enabled` metric and its statistics, see [Instance metrics](./viewing_metrics_with_cloudwatch.html#ec2-cloudwatch-metrics).
+