Skip to content

EKS clusters endpoint should restrict public access

Ensure whether AWS Elastic Kubernetes Service (AWS EKS) endpoint is not publicly accessible. The rule is compliant if the endpoint is publicly accessible.

How to fix

Attribute vpc_config[0].endpoint_public_access of aws_eks_cluster must be false.

Implementation options

Choose the option that matches how you manage Terraform. All options satisfy this control.

Use the compliance.tf registry module to get this control enforced by default. This control is mapped to the frameworks shown in the tabs above. To begin, see get started with compliance.tf.

module "eks" {
  source  = "cisv80ig1.compliance.tf/terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"
}

module "eks" {
  source  = "nist800171.compliance.tf/terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"
}

module "eks" {
  source  = "nistcsfv11.compliance.tf/terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"
}

module "eks" {
  source  = "pcidssv321.compliance.tf/terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"
}

module "eks" {
  source  = "pcidss.compliance.tf/terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"
}

Option 2: Open source module (terraform-aws-modules)

If you use terraform-aws-modules/eks/aws, configure the required module inputs to satisfy this control. You can later migrate to the compliance.tf module with minimal changes because it is compatible by design.

module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = ">=21.0.0"

  cluster_name = "abc123"
  subnet_ids   = ["subnet-abc123", "subnet-def456"]
  vpc_id       = "vpc-12345678"

  endpoint_public_access = false
}

Option 3: Terraform AWS provider resources

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_eks_cluster.

resource "aws_eks_cluster" "this" {
  enabled_cluster_log_types = ["api", "audit", "authenticator", "controllerManager", "scheduler"]

  encryption_config {
    provider {
      key_arn = "arn:aws:kms:us-east-1:123456789012:key/12345678-1234-1234-1234-123456789012"
    }
    resources = ["secrets"]
  }

  name     = "pofix-example"
  role_arn = "arn:aws:iam::123456789012:role/example-role"

  vpc_config {
    endpoint_public_access = false
    subnet_ids             = ["subnet-abc123", "subnet-def456"]
  }
}
Which option should I choose?
  • Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
  • Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
  • Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf (CTF) Control: eks_cluster_endpoint_restrict_public_access

  • AWS Config Managed Rule: EKS_ENDPOINT_NO_PUBLIC_ACCESS

  • Checkov Checks: CKV_AWS_38, CKV_AWS_39

  • Powerpipe Controls: aws_compliance.control.eks_cluster_endpoint_public_access_restricted, aws_compliance.control.eks_cluster_endpoint_restrict_public_access