MSK Broker Logging Disabled

What this rule checks

Detects MSK clusters without broker logs configured.

How to fix it

1. 1Enable broker logs to CloudWatch Logs, Firehose, or S3

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

const vpc = new ec2.Vpc(this, 'Vpc');
new msk.CfnCluster(this, 'Cluster', {
  clusterName: 'events',
  kafkaVersion: '3.6.0',
  numberOfBrokerNodes: 2,
  brokerNodeGroupInfo: { instanceType: 'kafka.m5.large', clientSubnets: vpc.privateSubnets.map((s) => s.subnetId) },
});

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

const vpc = new ec2.Vpc(this, 'Vpc');
new msk.CfnCluster(this, 'Cluster', {
  clusterName: 'events',
  kafkaVersion: '3.6.0',
  numberOfBrokerNodes: 2,
  brokerNodeGroupInfo: { instanceType: 'kafka.m5.large', clientSubnets: vpc.privateSubnets.map((s) => s.subnetId) },
  loggingInfo: { brokerLogs: { cloudWatchLogs: { enabled: true, logGroup: 'msk-broker-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 msk-broker-logging-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID msk-broker-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 MSK rules