Ensure AWS EKS cluster security group is not overly permissive to all traffic

Error: AWS EKS cluster security group overly permissive to all traffic

Bridgecrew Policy ID: BC_AWS_KUBERNETES_1
Checkov Check ID: CKV_AWS_38
Severity: HIGH

AWS EKS cluster security group overly permissive to all traffic

Description

Amazon EKS creates an endpoint for any managed Kubernetes API server to communicate with the cluster. By default, this API server endpoint is public to the internet. Access to it should be regulated using AWS IAM and native Kubernetes RBAC.

We recommend that your Kubernetes API server remains private so that all communication between worker nodes and APIs stays within your VPC. If public access is needed, at a minimum, restrict the IP addresses that can access your API server from the internet to reduce the potential attack surface. Ensure your Amazon EKS public endpoint is not accessible to 0.0.0.0/0.

Fix - Runtime

Amazon Console

  1. Login to the AWS Management Console at https://console.aws.amazon.com/.
  2. Open the Amazon EKS console.
  3. To display your cluster information, select the cluster's name.
  4. Navigate to Networking, select Update.
  5. Select Private Access or Public Access.
    Private access. Select whether to enable or disable private access for your cluster's Kubernetes API server endpoint. If you enable private access, Kubernetes API requests that originate from within your cluster's VPC use the private VPC endpoint. You must enable private access to disable public access.
    Public access. Select whether to enable or disable public access for your cluster's Kubernetes API server endpoint. If you disable public access, your cluster's Kubernetes API server can only receive requests from within the cluster VPC.
  6. Click Advanced Settings.
  7. To enter a CIDR block or add additional blocks, select Add Source. If you specify no blocks, the public API server endpoint receives requests from all (0.0.0.0/0) IP addresses.
  8. To finish, click Update.

Did this page help you?