Other Articles

EKS Cluster – Enable Control Plane Logging

Secure Configuration Checks > AWS

This check ensures that the API server, audit and authenticator control plane logs of an Amazon EKS cluster are enabled. Without these logs, you cannot see who called the Kubernetes API, what they changed or how they signed in.

Check Details

  • Resource: EKS Cluster
  • Check: Enable EKS cluster control plane logging (ControlPlaneLoggingEnabled)
  • Risk: Attacks and misuse of the cluster go unnoticed, and you have no evidence for an investigation

Log types

  • API server (api): Logs of the Kubernetes API server. Required by this check.
  • Audit (audit): A record of the requests made to the API, by whom and when. Required by this check.
  • Authenticator (authenticator): Logs of IAM-based authentication to the cluster. Required by this check.
  • Controller manager (controllerManager): Logs of the Kubernetes controllers. Optional.
  • Scheduler (scheduler): Logs of pod scheduling decisions. Optional.

Remediation via AWS Console

  1. Open the Amazon EKS console and select the affected cluster.

    Amazon EKS Console
  2. Open the Configuration tab and locate the Control plane logs section.

  3. Click Manage and enable API server, Audit, and Authenticator logs. Optionally enable Controller manager and Scheduler.

    Manage EKS control plane logging
  4. Click Save changes and verify that the selected log types are enabled.

  5. Repeat for every affected cluster.

Note: Control plane logs are sent to Amazon CloudWatch Logs. Standard CloudWatch ingestion and storage charges apply.

Remediation via AWS CLI

  1. Log in to the AWS Management Console and click the CloudShell icon (>_) in the top-right corner.

    AWS CloudShell
  2. List the clusters where one of the three required log types is not enabled:

    for c in $(aws eks list-clusters --query 'clusters[]' --output text); do
      aws eks describe-cluster --name "$c" --output json | \
      jq -r '.cluster
        | ([.logging.clusterLogging[] | select(.enabled == true) | .types[]]) as $on
        | select(any(["api","audit","authenticator"][]; . as $t | ($on | index($t)) == null))
        | .name'
    done
    

    The command covers one region. Add --region <region> to each aws command to check another.

  3. Enable the required log types:

    aws eks update-cluster-config \
    --name <cluster-name> \
    --logging '{"clusterLogging":[{"types":["api","audit","authenticator"],"enabled":true}]}'
    

    To also enable the optional logs, add "controllerManager" and "scheduler" to the types list.

    Wait for the update to finish:

    aws eks wait cluster-active --name <cluster-name>
    
  4. Set a retention period on the log group. By default CloudWatch keeps the logs forever:

    aws logs put-retention-policy \
    --log-group-name /aws/eks/<cluster-name>/cluster \
    --retention-in-days <days>
    
  5. Verify the logging configuration:

    aws eks describe-cluster \
    --name <cluster-name> \
    --query 'cluster.logging'
    

Replace <cluster-name> with the name of the cluster, for example prod-cluster. Replace <days> with the number of days to keep the logs, for example 365. Repeat steps 3 to 5 for each cluster.

Updated on 03 November, 2026