Ensure EKS node groups use managed node groups
EKS should use managed node groups for automatic patching, updates, and simplified management.
Security Impact
Self-managed nodes require manual patching and may fall behind on security updates.
How to Remediate
Migrate self-managed node groups to EKS managed node groups for automated patching.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Elastic Kubernetes Service (EKS) resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-eks-4
- Service
- Elastic Kubernetes Service (EKS)
- Category
- Patch Management
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Elastic Kubernetes Service (EKS) Checks
View all checksEnsure EKS cluster endpoint is not publicly accessible
Ensure EKS cluster has secrets encryption enabled
Ensure EKS cluster logging is enabled
Ensure EKS clusters use the latest Kubernetes version
Ensure EKS node groups use current AMI versions