RDS Instance Using gp2 Storage

What this rule checks

Detects Multi-AZ RDS instances on gp2 storage; gp3 offers better baseline performance at lower cost.

How to fix it

1. 1Migrate the instance storage type from gp2 to gp3
2. 2Right-size provisioned IOPS/throughput for gp3

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

new rds.CfnDBInstance(this, 'Db', {
  engine: 'postgres',
  dbInstanceClass: 'db.m5.large',
  allocatedStorage: '100',
  multiAz: true,
  storageType: 'gp2',
});

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

new rds.CfnDBInstance(this, 'Db', {
  engine: 'postgres',
  dbInstanceClass: 'db.m5.large',
  allocatedStorage: '100',
  multiAz: true,
  storageType: 'gp3',
});

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

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "rds-multi-az-gp2-storage", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

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

Use the rule ID rds-multi-az-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 RDS rules