EKS Control Plane Logging Disabled
API server activity is not recorded, so cluster-level changes and access cannot be audited.
Free to start. No card. The playground just needs your work email.
AWSKubernetes
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable control-plane logging on EKS cluster.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EKS Clusters on AWS
- The fix, by hand
- EKS → Clusters → the resource → Observability → Manage logging.
- Enable at least one (ideally all five) control-plane log types: api, audit, authenticator, controllerManager, scheduler.
- CloudWatch → Log groups → /aws/eks/‹cluster›/cluster. Set retention (≥90 days for prod, 30 days for dev).
- Optionally configure a subscription filter to ship logs to your SIEM / S3.
- This finding is re-evaluated from the cluster's live logging configuration on the next discovery run. No manual tag is needed; once a log type is enabled it stops firing on its own.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-062- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.