Ensuring that EKS (Elastic Kubernetes Service) Private access is enabled means that your Kubernetes cluster's control plane and worker nodes can communicate privately over an Amazon VPC (Virtual Private Cloud) endpoint without being exposed to the public internet. This helps to enhance the security posture of your EKS cluster by minimizing the attack surface area and reducing the risk of unauthorized access to the cluster's control plane and worker nodes. It is recommended to enable EKS Private access in environments where security and privacy are critical requirements.


To ensure that EKS Private access is enabled, follow these steps:

  1. Log in to the AWS Management Console and navigate to the Amazon EKS console.
  2. Select the EKS cluster for which you want to enable Private access.
  3. Click on the "Networking" tab.
  4. Under "Cluster security group", click on "Edit".
  5. In the "Edit cluster security group" dialog box, select "Allow all traffic" or "Custom" and add rules to allow traffic from your VPC CIDR range and VPC endpoint security group.
  6. Click "Save" to apply the changes.
  7. Ensure that the worker nodes and control plane have been launched within the same VPC and subnet as the endpoint.
  8. Verify that the EKS cluster can be accessed privately by running a test pod in the EKS cluster and verifying that it can communicate with the control plane without being exposed to the public internet.

Enabling EKS Private access can help to improve security by preventing unauthorized access to the cluster's control plane and worker nodes over the public internet.

Enforced Resources
Note: Remediation steps provided by Lightlytics are meant to be suggestions and guidelines only. It is crucial to thoroughly verify and test any remediation steps before applying them to production environments. Each organization's infrastructure and security needs may differ, and blindly applying suggested remediation steps without proper testing could potentially cause unforeseen issues or vulnerabilities. Therefore, it is strongly recommended that you validate and customize any remediation steps to meet your organization's specific requirements and ensure that they align with your security policies and best practices.