Skip to main content
MEDIUMEKSSecurity

EKS Control Plane Logging Disabled

eks-control-plane-logging-disabled

What this rule checks

Detects EKS clusters with no control plane log types enabled.

How to fix it

  1. 1Enable api, audit, authenticator, controllerManager, and scheduler logs
FlaggedNo Logging.ClusterLogging.EnabledTypes are declared, so none of the control plane log streams reach CloudWatch. The check flags any EKS cluster with zero control plane log types enabled.
import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as eks from 'aws-cdk-lib/aws-eks';

// FLAGGED: cluster created with no control plane logging.
new eks.CfnCluster(this, 'Cluster', {
  roleArn: 'arn:aws:iam::123456789012:role/eks-cluster-role',
  resourcesVpcConfig: { subnetIds: ['subnet-0aaaa', 'subnet-0bbbb'] },
});
FixedEnabling all five recommended control plane log types (api, audit, authenticator, controllerManager, scheduler) sends full audit and diagnostic logs to CloudWatch and clears both the missing-types and no-logging findings.
import { App, Stack } from 'aws-cdk-lib';
import { Construct } from 'constructs';
import * as eks from 'aws-cdk-lib/aws-eks';

// FIXED: all five control plane log types enabled.
new eks.CfnCluster(this, 'Cluster', {
  roleArn: 'arn:aws:iam::123456789012:role/eks-cluster-role',
  resourcesVpcConfig: { subnetIds: ['subnet-0aaaa', 'subnet-0bbbb'] },
  logging: {
    clusterLogging: {
      enabledTypes: [
        { type: 'api' },
        { type: 'audit' },
        { type: 'authenticator' },
        { type: 'controllerManager' },
        { type: 'scheduler' },
      ],
    },
  },
});

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

AWS::EKS::Cluster

Compliance frameworks

SOC2HIPAAPCI-DSSNIST

AWS documentation

Read the AWS guidance

Intentional? Suppress this finding

Sometimes a flag is deliberate โ€” a genuinely public endpoint, say. You can dismiss eks-control-plane-logging-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID eks-control-plane-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 โ†’

Catch this in your stack

$ npx cdk-insights scan

CDK Insights runs this and 118+ other rules locally against your synthesised CDK app โ€” free, no account, your code never leaves your machine.

More EKS rules