ELB Deletion Protection Disabled

What this rule checks

Detects load balancers without deletion protection.

How to fix it

1. 1Enable deletion protection for production load balancers
2. 2Use CloudFormation DeletionPolicy: Retain

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

const vpc = new ec2.Vpc(this, 'Vpc');
new elbv2.ApplicationLoadBalancer(this, 'Alb', { vpc });

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

const vpc = new ec2.Vpc(this, 'Vpc');
new elbv2.ApplicationLoadBalancer(this, 'Alb', { vpc, deletionProtection: true });

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 elb-deletion-protection-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "elb-deletion-protection-disabled", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::elb-deletion-protection-disabled',
  reason: 'Why this is intentional',
});

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

More ELB rules