# Ensure Access is restrict to the EKS Control Plane Endpoint

- Source: https://support.icompaas.com/support/solutions/articles/62000229617-ensure-access-is-restrict-to-the-eks-control-plane-endpoint
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Policy Updates](https://support.icompaas.com/support/solutions/folders/62000168784)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Description:**

Amazon Elastic Kubernetes Service (EKS) control plane endpoints are the only way to access the Kubernetes API server for an EKS cluster. By default, these endpoints are public, which means that anyone can access them. This can be a security risk, as it allows unauthorized users to access the API server.

**Rationale:**

Restricting access to the EKS control plane endpoint can help to improve the security of your clusters. This will make it more difficult for unauthorized users to access the API server.

**Impact:**

Restricting access to the EKS control plane endpoint will prevent unauthorized users from accessing the Kubernetes API server. This can help to protect your cluster from unauthorized changes and attacks.

**Default Value:**

By default, EKS control plane endpoints are public. You must explicitly restrict access to them.

**Pre-Requisite:**

To follow this policy, you will need to have access to the AWS Management Console or the AWS CLI. You will also need to know the VPC that you want to use for the EKS cluster.

**Remediation Steps:**

To remediate this issue, you can follow these steps:

1.  In the AWS Management Console, go to the **EKS** page.
2.  Select the cluster that you want to update.
3.  Click the **Networking** tab.
4.  For **Private endpoint**, select **Enabled**.
5.  For **Public access**, select **Disabled**.
6.  Click **Save**.

**Test Plan:**

To test that the policy has been implemented correctly, you can use the following steps:

1.  Check the EKS cluster logs to see if the private endpoint is being used.
2.  Verify that you cannot access the Kubernetes API server from outside of the VPC.

**Implementation Plan:**

The following are the steps on how to implement this policy:

1.  Identify the EKS clusters that are not created with private endpoints enabled and public access disabled.
2.  Enable private endpoints and disable public access for the EKS clusters.
3.  Test that the policy has been implemented correctly.

**AWS CLI Process:**

To enable private endpoints and disable public access for an EKS cluster using the AWS CLI, you can use the following command:

```
aws eks update-cluster --name my-cluster --enable-private-endpoint --disable-public-access
```

**Using AWS GUI:**

To enable private endpoints and disable public access for an EKS cluster using the AWS GUI, you can follow these steps:

1.  Go to the AWS Management Console.
2.  Click on the **EKS** service.
3.  Click on the **Clusters** tab.
4.  Select the cluster that you want to update.
5.  Click on the **Networking** tab.
6.  For **Private endpoint**, select **Enabled**.
7.  For **Public access**, select **Disabled**.
8.  Click on the **Save** button.

**Backout Plan:**

To revoke the changes that you made to the private endpoint configuration in an EKS cluster, you can follow these steps:

1.  In the AWS Management Console, go to the **EKS** page.
2.  Select the cluster that you want to update.
3.  Click the **Networking** tab.
4.  For **Private endpoint**, select **Disabled**.
5.  For **Public access**, select **Enabled**.
6.  Click **Save**.

**Note:**

-   You can also use the AWS CLI or the AWS GUI to enable private endpoints and disable public access for all EKS clusters in your account.
-   If you disable private endpoints or enable public access, you will lose the ability to restrict access to the Kubernetes API server to your VPC.

**Reference:**

-   AWS documentation on EKS private endpoints: https://docs.aws.amazon.com/eks/latest/userguide/private-clusters.html

**Section 2:**

-   Tags: security, EKS, private endpoint, public access
-   Keywords: remediation, backout, policy, cluster

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
