Multiple NAT Gateways

What this rule checks

Detects stacks with three or more NAT Gateways — a recurring cost driver that often has cheaper alternatives.

How to fix it

1. 1Audit NAT Gateway count; consider NAT instances for dev environments or VPC endpoints for AWS service traffic

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 stack-multiple-nat-gateways and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "stack-multiple-nat-gateways", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::stack-multiple-nat-gateways',
  reason: 'Why this is intentional',
});

Use the rule ID stack-multiple-nat-gateways 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