EC2 Instance Type Outdated

What this rule checks

Detects EC2 instances using older generation instance types.

How to fix it

1. 1Upgrade to current generation instance types
2. 2Use AWS Compute Optimizer for recommendations

import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as ec2 from 'aws-cdk-lib/aws-ec2';

// FLAGGED: L1 instance pinned to a previous-generation t2 type.
new ec2.CfnInstance(this, 'AppServer', {
  instanceType: 't2.micro',
  imageId: 'ami-0abcdef1234567890',
});

import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as ec2 from 'aws-cdk-lib/aws-ec2';

// FIXED: current-generation t3 (Nitro) instance type.
new ec2.CfnInstance(this, 'AppServer', {
  instanceType: 't3.micro',
  imageId: 'ami-0abcdef1234567890',
});

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-instance-type-outdated and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "ec2-instance-type-outdated", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::ec2-instance-type-outdated',
  reason: 'Why this is intentional',
});

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

More EC2 rules