Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
eks_cluster_not_publicly_accessibleProvider: AWS
Service:
eksSeverity: HIGH
Categories:
internet-exposed, cluster-securityResource type:
AwsEksClusterWhat this check verifies
Amazon EKS cluster API server endpoint is evaluated for unrestricted Internet access, specifically when the public endpoint permits connections from0.0.0.0/0 instead of private access or limited CIDR ranges.
Risk
An openly reachable API endpoint enables Internet-wide probing, brute force, and enumeration, increasing exposure to RBAC misconfigurations or API flaws. Successful access can drive secret exfiltration (confidentiality), workload tampering (integrity), and control-plane disruption or scaling abuse (availability, cost).Recommendation
Prefer private endpoint access and avoid broad exposure. If public access is required, restrict to trusted admin CIDRs (not0.0.0.0/0), reach the API via VPN/Direct Connect or bastions, and enforce least privilege with IAM/RBAC. Apply defense in depth through network segmentation and continuous monitoring.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://docs.aws.amazon.com/eks/latest/eksctl/vpc-cluster-access.html
- https://docs.aws.amazon.com/eks/latest/userguide/config-cluster-endpoint.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/EKS/endpoint-access.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = eks_cluster_not_publicly_accessible. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks