EBS Volume On gp2 Storage

What this rule checks

Detects EBS volumes using gp2 where gp3 offers the same baseline for less.

How to fix it

1. 1Set VolumeType to gp3 (and tune IOPS/Throughput independently if needed)

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 ebs-volume-gp2-storage and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "ebs-volume-gp2-storage", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::ebs-volume-gp2-storage',
  reason: 'Why this is intentional',
});

Use the rule ID ebs-volume-gp2-storage 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