EC2 IMDSv2 Not Enforced

What this rule checks

Detects launch templates and launch configurations that do not require IMDSv2 (MetadataOptions.HttpTokens is not "required"), leaving instances exposed to SSRF-based credential theft.

How to fix it

1. 1Set MetadataOptions.HttpTokens to "required" on the launch template / launch configuration
2. 2In CDK, pass requireImdsv2: true on the instance or launch template

import * as ec2 from 'aws-cdk-lib/aws-ec2';

new ec2.CfnLaunchTemplate(this, 'Lt', {
  launchTemplateData: {
    instanceType: 't3.micro',
  },
});

import * as ec2 from 'aws-cdk-lib/aws-ec2';

new ec2.CfnLaunchTemplate(this, 'Lt', {
  launchTemplateData: {
    instanceType: 't3.micro',
    metadataOptions: { httpTokens: 'required' },
  },
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

Intentional? Suppress this finding

Sometimes a flag is deliberate — a genuinely public endpoint, say. You can dismiss ec2-imdsv2-not-enforced and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "ec2-imdsv2-not-enforced", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::ec2-imdsv2-not-enforced',
  reason: 'Why this is intentional',
});

Use the rule ID ec2-imdsv2-not-enforced shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More Cross-service rules