EKS abstracts Kubernetes control plane management, but security remains your responsibility. Risks include overly permissive roles, exposed APIs, and insecure container workloads. Strong configuration and isolation are required.
Allowing public access to the EKS hosted Kubernetes API endpoint is a substantially worse security posture than utilising private API endpoints
AWS EKS utilises a Container Network Interface designed for EC2, which consumes a significant number of IP addresses that the network must accommodate.
EKS Clusters should remain updated to prevent publicly exposed APIs from compromise and avoid forced updates which can break service
