ELB Logging Disabled

What this rule checks

Detects load balancers without access logging.

How to fix it

1. 1Enable access logging to S3
2. 2Configure log retention policy

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

new elbv2.CfnLoadBalancer(this, 'Alb', {
  type: 'application',
  subnets: ['subnet-aaaa1111', 'subnet-bbbb2222'],
});

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

new elbv2.CfnLoadBalancer(this, 'Alb', {
  type: 'application',
  subnets: ['subnet-aaaa1111', 'subnet-bbbb2222'],
  loadBalancerAttributes: [
    { key: 'access_logs.s3.enabled', value: 'true' },
    { key: 'access_logs.s3.bucket', value: 'my-alb-logs' },
  ],
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID elb-logging-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