Overview
The AWS EKS integration ingests EKS control plane logs that are streamed to CloudWatch Logs:api: Kubernetes API server requestsaudit: admission and authorization decisionsauthenticator: IAM-to-Kubernetes identity mapping eventscontrollerManager: controller reconcile loopsscheduler: pod scheduling decisions
Prerequisites
- An EKS cluster with control plane logging enabled.
- IAM credentials with read access to the cluster’s log group.
Step 1: Enable EKS control plane logging
- Open the AWS Console → EKS → Clusters and select your cluster.
- Open the Observability tab.
- Under Control plane logging, click Manage logging and enable the log types you need:
- API server
- Audit
- Authenticator
- Controller manager
- Scheduler
- Click Save changes. EKS will create a log group named
/aws/eks/<cluster-name>/cluster.
Step 2: Create an IAM user with log read access
- Open IAM → Users → Create user, name it
atatus-eks-reader. - Attach an inline policy granting:
logs:DescribeLogGroupslogs:DescribeLogStreamslogs:GetLogEventslogs:FilterLogEvents
- Scope the policy to the EKS log group ARN.
- Create an access key under Security credentials → Create access key and copy both values.
Step 3: Connect AWS EKS in Atatus
- In Atatus, go to Security → Cloud SIEM → Integrations.
- Locate the AWS EKS card and click Connect.
- Fill in the form:
- Click Connect.
Verification
- The AWS EKS card shows Configured.
- Control plane events appear in Security → Cloud SIEM → Audit Logs → Events with source
aws_eks.