{"id":14957858,"url":"https://github.com/cloudposse/terraform-aws-eks-cluster","last_synced_at":"2026-04-02T15:57:15.170Z","repository":{"id":38855211,"uuid":"140049633","full_name":"cloudposse/terraform-aws-eks-cluster","owner":"cloudposse","description":"Terraform module for provisioning an EKS cluster","archived":false,"fork":false,"pushed_at":"2025-02-19T21:54:03.000Z","size":4620,"stargazers_count":531,"open_issues_count":6,"forks_count":360,"subscribers_count":27,"default_branch":"main","last_synced_at":"2025-04-13T20:44:25.635Z","etag":null,"topics":["aws","eks","eks-cluster","eks-workers","fargate","hcl2","k8s","kubernetes","masters","terraform","terraform-module"],"latest_commit_sha":null,"homepage":"https://cloudposse.com/accelerate","language":"HCL","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cloudposse.png","metadata":{"funding":{"github":"cloudposse"},"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":"security-group.tf","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-07-07T03:30:29.000Z","updated_at":"2025-04-07T16:08:59.000Z","dependencies_parsed_at":"2023-11-15T04:22:25.498Z","dependency_job_id":"2a07c992-bfd5-4d8a-9850-4cfad988da8f","html_url":"https://github.com/cloudposse/terraform-aws-eks-cluster","commit_stats":{"total_commits":124,"total_committers":43,"mean_commits":2.883720930232558,"dds":0.8306451612903226,"last_synced_commit":"5a6095f2741027f65ecb4cdfaa1d3ee43402cdc2"},"previous_names":[],"tags_count":97,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-eks-cluster","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-eks-cluster/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-eks-cluster/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cloudposse%2Fterraform-aws-eks-cluster/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cloudposse","download_url":"https://codeload.github.com/cloudposse/terraform-aws-eks-cluster/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248782280,"owners_count":21160716,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["aws","eks","eks-cluster","eks-workers","fargate","hcl2","k8s","kubernetes","masters","terraform","terraform-module"],"created_at":"2024-09-24T13:15:43.362Z","updated_at":"2026-04-02T15:57:15.156Z","avatar_url":"https://github.com/cloudposse.png","language":"HCL","funding_links":["https://github.com/sponsors/cloudposse"],"categories":[],"sub_categories":[],"readme":"\n\n\u003c!-- markdownlint-disable --\u003e\n\u003ca href=\"https://cpco.io/homepage\"\u003e\u003cimg src=\"https://github.com/cloudposse/terraform-aws-eks-cluster/blob/main/.github/banner.png?raw=true\" alt=\"Project Banner\"/\u003e\u003c/a\u003e\u003cbr/\u003e\n\n\n\u003cp align=\"right\"\u003e\u003ca href=\"https://github.com/cloudposse/terraform-aws-eks-cluster/releases/latest\"\u003e\u003cimg src=\"https://img.shields.io/github/release/cloudposse/terraform-aws-eks-cluster.svg?style=for-the-badge\" alt=\"Latest Release\"/\u003e\u003c/a\u003e\u003ca href=\"https://github.com/cloudposse/terraform-aws-eks-cluster/commits\"\u003e\u003cimg src=\"https://img.shields.io/github/last-commit/cloudposse/terraform-aws-eks-cluster.svg?style=for-the-badge\" alt=\"Last Updated\"/\u003e\u003c/a\u003e\u003ca href=\"https://cloudposse.com/slack\"\u003e\u003cimg src=\"https://slack.cloudposse.com/for-the-badge.svg\" alt=\"Slack Community\"/\u003e\u003c/a\u003e\u003ca href=\"https://cloudposse.com/support/\"\u003e\u003cimg src=\"https://img.shields.io/badge/Get_Support-success.svg?style=for-the-badge\" alt=\"Get Support\"/\u003e\u003c/a\u003e\n\n\u003c/p\u003e\n\u003c!-- markdownlint-restore --\u003e\n\n\u003c!--\n\n\n\n\n  ** DO NOT EDIT THIS FILE\n  **\n  ** This file was automatically generated by the `cloudposse/build-harness`.\n  ** 1) Make all changes to `README.yaml`\n  ** 2) Install [atmos](https://atmos.tools/install/) (you only need to do this once)\n  ** 3) Run`atmos readme` to rebuild this file.\n  **\n  ** (We maintain HUNDREDS of open source projects. This is how we maintain our sanity.)\n  **\n\n\n\n\n\n--\u003e\n\nTerraform module to provision an [EKS](https://aws.amazon.com/eks/) cluster on AWS.\n\u003cbr/\u003e\u003cbr/\u003e\nThis Terraform module provisions a fully configured AWS [EKS](https://aws.amazon.com/eks/) (Elastic Kubernetes Service) cluster.\nIt's engineered to integrate smoothly with [Karpenter](https://karpenter.sh/) and [EKS addons](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html),\nforming a critical part of [Cloud Posse's reference architecture](https://cloudposse.com/reference-architecture).\nIdeal for teams looking to deploy scalable and manageable Kubernetes clusters on AWS with minimal fuss.\n\n\n\u003e [!TIP]\n\u003e #### 👽 Use Atmos with Terraform\n\u003e Cloud Posse uses [`atmos`](https://atmos.tools) to easily orchestrate multiple environments using Terraform. \u003cbr/\u003e\n\u003e Works with [Github Actions](https://atmos.tools/integrations/github-actions/), [Atlantis](https://atmos.tools/integrations/atlantis), or [Spacelift](https://atmos.tools/integrations/spacelift).\n\u003e\n\u003e \u003cdetails\u003e\n\u003e \u003csummary\u003e\u003cstrong\u003eWatch demo of using Atmos with Terraform\u003c/strong\u003e\u003c/summary\u003e\n\u003e \u003cimg src=\"https://github.com/cloudposse/atmos/blob/main/docs/demo.gif?raw=true\"/\u003e\u003cbr/\u003e\n\u003e \u003ci\u003eExample of running \u003ca href=\"https://atmos.tools\"\u003e\u003ccode\u003eatmos\u003c/code\u003e\u003c/a\u003e to manage infrastructure from our \u003ca href=\"https://atmos.tools/quick-start/\"\u003eQuick Start\u003c/a\u003e tutorial.\u003c/i\u003e\n\u003e \u003c/detalis\u003e\n\n\n## Introduction\n\nThe module provisions the following resources:\n\n- EKS cluster of master nodes that can be used together with the\n  [terraform-aws-eks-node-group](https://github.com/cloudposse/terraform-aws-eks-node-group) and\n  [terraform-aws-eks-fargate-profile](https://github.com/cloudposse/terraform-aws-eks-fargate-profile)\n  modules to create a full-blown EKS/Kubernetes cluster. You can also use the [terraform-aws-eks-workers](https://github.com/cloudposse/terraform-aws-eks-workers)\n  module to provision worker nodes for the cluster, but it is now rare for that to be a better choice than to use `terraform-aws-eks-node-group`.\n- IAM Role to allow the cluster to access other AWS services\n- EKS access entries to allow IAM users to access and administer the cluster\n\n\n\n\n## Usage\n\nFor a complete example, see [examples/complete](examples/complete).\n\nFor automated tests of the complete example using [bats](https://github.com/bats-core/bats-core) and [Terratest](https://github.com/gruntwork-io/terratest) (which tests and deploys the example on AWS), see [test/src](test/src).\n\nOther examples:\n\n- [terraform-aws-components/eks/cluster](https://github.com/cloudposse/terraform-aws-components/tree/master/modules/eks/cluster) - Cloud Posse's service catalog of \"root module\" invocations for provisioning reference architectures\n\n```hcl\n  provider \"aws\" {\n    region = var.region\n  }\n\n  # Note: This example creates an explicit access entry for the current user,\n  # but in practice, you should use a static map of IAM users or roles that should have access to the cluster.\n  # Granting access to the current user in this way is not recommended for production use.\n  data \"aws_caller_identity\" \"current\" {}\n\n  # IAM session context converts an assumed role ARN into an IAM Role ARN.\n  # Again, this is primarily to simplify the example, and in practice, you should use a static map of IAM users or roles.\n  data \"aws_iam_session_context\" \"current\" {\n    arn = data.aws_caller_identity.current.arn\n  }\n\n  locals {\n    # The usage of the specific kubernetes.io/cluster/* resource tags below are required\n    # for EKS and Kubernetes to discover and manage networking resources\n    # https://aws.amazon.com/premiumsupport/knowledge-center/eks-vpc-subnet-discovery/\n    # https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/docs/deploy/subnet_discovery.md\n    tags = { \"kubernetes.io/cluster/${module.label.id}\" = \"shared\" }\n\n    # required tags to make ALB ingress work https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html\n    public_subnets_additional_tags = {\n      \"kubernetes.io/role/elb\" : 1\n    }\n    private_subnets_additional_tags = {\n      \"kubernetes.io/role/internal-elb\" : 1\n    }\n\n    # Enable the IAM user creating the cluster to administer it,\n    # without using the bootstrap_cluster_creator_admin_permissions option,\n    # as an example of how to use the access_entry_map feature.\n    # In practice, this should be replaced with a static map of IAM users or roles\n    # that should have access to the cluster, but we use the current user\n    # to simplify the example.\n    access_entry_map = {\n      (data.aws_iam_session_context.current.issuer_arn) = {\n        access_policy_associations = {\n          ClusterAdmin = {}\n        }\n      }\n    }\n  }\n\n  module \"label\" {\n    source = \"cloudposse/label/null\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version  = \"x.x.x\"\n\n    namespace  = var.namespace\n    name       = var.name\n    stage      = var.stage\n    delimiter  = var.delimiter\n    tags       = var.tags\n  }\n\n  module \"vpc\" {\n    source = \"cloudposse/vpc/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    ipv4_primary_cidr_block = \"172.16.0.0/16\"\n\n    tags    = local.tags\n    context = module.label.context\n  }\n\n  module \"subnets\" {\n    source = \"cloudposse/dynamic-subnets/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    availability_zones   = var.availability_zones\n    vpc_id               = module.vpc.vpc_id\n    igw_id               = [module.vpc.igw_id]\n    ipv4_cidr_block      = [module.vpc.vpc_cidr_block]\n    nat_gateway_enabled  = true\n    nat_instance_enabled = false\n\n    public_subnets_additional_tags  = local.public_subnets_additional_tags\n    private_subnets_additional_tags = local.private_subnets_additional_tags\n\n    tags    = local.tags\n    context = module.label.context\n  }\n\n  module \"eks_node_group\" {\n    source = \"cloudposse/eks-node-group/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    instance_types    = [var.instance_type]\n    subnet_ids        = module.subnets.private_subnet_ids\n    health_check_type = var.health_check_type\n    min_size          = var.min_size\n    max_size          = var.max_size\n    cluster_name      = module.eks_cluster.eks_cluster_id\n\n    # Enable the Kubernetes cluster auto-scaler to find the auto-scaling group\n    cluster_autoscaler_enabled = var.autoscaling_policies_enabled\n\n    context = module.label.context\n  }\n\n  module \"eks_cluster\" {\n    source = \"cloudposse/eks-cluster/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version = \"x.x.x\"\n\n    subnet_ids            = concat(module.subnets.private_subnet_ids, module.subnets.public_subnet_ids)\n    kubernetes_version    = var.kubernetes_version\n    oidc_provider_enabled = true\n\n    addons = [\n      # https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html#vpc-cni-latest-available-version\n      {\n        addon_name                  = \"vpc-cni\"\n        addon_version               = var.vpc_cni_version\n        resolve_conflicts_on_create = \"OVERWRITE\"\n        resolve_conflicts_on_update = \"OVERWRITE\"\n        service_account_role_arn    = var.vpc_cni_service_account_role_arn # Creating this role is outside the scope of this example\n      },\n      # https://docs.aws.amazon.com/eks/latest/userguide/managing-kube-proxy.html\n      {\n        addon_name                  = \"kube-proxy\"\n        addon_version               = var.kube_proxy_version\n        resolve_conflicts_on_create = \"OVERWRITE\"\n        resolve_conflicts_on_update = \"OVERWRITE\"\n        service_account_role_arn    = null\n      },\n      # https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html\n      {\n        addon_name                  = \"coredns\"\n        addon_version               = var.coredns_version\n        resolve_conflicts_on_create = \"OVERWRITE\"\n        resolve_conflicts_on_update = \"OVERWRITE\"\n        service_account_role_arn    = null\n      },\n    ]\n    addons_depends_on = [module.eks_node_group]\n\n    context = module.label.context\n\n    cluster_depends_on = [module.subnets]\n  }\n```\n\nModule usage with two unmanaged worker groups:\n\n```hcl\n  locals {\n    # Unfortunately, the `aws_ami` data source attribute `most_recent` (https://github.com/cloudposse/terraform-aws-eks-workers/blob/34a43c25624a6efb3ba5d2770a601d7cb3c0d391/main.tf#L141)\n    # does not work as you might expect. If you are not going to use a custom AMI you should\n    # use the `eks_worker_ami_name_filter` variable to set the right kubernetes version for EKS workers,\n    # otherwise the first version of Kubernetes supported by AWS (v1.11) for EKS workers will be selected, but the\n    # EKS control plane will ignore it to use one that matches the version specified by the `kubernetes_version` variable.\n    eks_worker_ami_name_filter = \"amazon-eks-node-${var.kubernetes_version}*\"\n  }\n\n  module \"eks_workers\" {\n    source = \"cloudposse/eks-workers/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    attributes                         = [\"small\"]\n    instance_type                      = \"t3.small\"\n    eks_worker_ami_name_filter         = local.eks_worker_ami_name_filter\n    vpc_id                             = module.vpc.vpc_id\n    subnet_ids                         = module.subnets.public_subnet_ids\n    health_check_type                  = var.health_check_type\n    min_size                           = var.min_size\n    max_size                           = var.max_size\n    wait_for_capacity_timeout          = var.wait_for_capacity_timeout\n    cluster_name                       = module.label.id\n    cluster_endpoint                   = module.eks_cluster.eks_cluster_endpoint\n    cluster_certificate_authority_data = module.eks_cluster.eks_cluster_certificate_authority_data\n    cluster_security_group_id          = module.eks_cluster.eks_cluster_managed_security_group_id\n\n    # Auto-scaling policies and CloudWatch metric alarms\n    autoscaling_policies_enabled           = var.autoscaling_policies_enabled\n    cpu_utilization_high_threshold_percent = var.cpu_utilization_high_threshold_percent\n    cpu_utilization_low_threshold_percent  = var.cpu_utilization_low_threshold_percent\n\n    context = module.label.context\n  }\n\n  module \"eks_workers_2\" {\n    source = \"cloudposse/eks-workers/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    attributes                         = [\"medium\"]\n    instance_type                      = \"t3.medium\"\n    eks_worker_ami_name_filter         = local.eks_worker_ami_name_filter\n    vpc_id                             = module.vpc.vpc_id\n    subnet_ids                         = module.subnets.public_subnet_ids\n    health_check_type                  = var.health_check_type\n    min_size                           = var.min_size\n    max_size                           = var.max_size\n    wait_for_capacity_timeout          = var.wait_for_capacity_timeout\n    cluster_name                       = module.label.id\n    cluster_endpoint                   = module.eks_cluster.eks_cluster_endpoint\n    cluster_certificate_authority_data = module.eks_cluster.eks_cluster_certificate_authority_data\n    cluster_security_group_id          = module.eks_cluster.eks_cluster_managed_security_group_id\n\n    # Auto-scaling policies and CloudWatch metric alarms\n    autoscaling_policies_enabled           = var.autoscaling_policies_enabled\n    cpu_utilization_high_threshold_percent = var.cpu_utilization_high_threshold_percent\n    cpu_utilization_low_threshold_percent  = var.cpu_utilization_low_threshold_percent\n\n    context = module.label.context\n  }\n\n  module \"eks_cluster\" {\n    source = \"cloudposse/eks-cluster/aws\"\n    # Cloud Posse recommends pinning every module to a specific version\n    # version     = \"x.x.x\"\n\n    subnet_ids            = concat(module.subnets.private_subnet_ids, module.subnets.public_subnet_ids)\n    kubernetes_version    = var.kubernetes_version\n    oidc_provider_enabled = true # needed for VPC CNI\n\n    access_entries_for_nodes = {\n      EC2_LINUX = [module.eks_workers.workers_role_arn, module.eks_workers_2.workers_role_arn]\n    }\n\n    context = module.label.context\n  }\n```\n\n\u003e [!WARNING]\n\u003e Release `4.0.0` contains major breaking changes that will require you to update your existing EKS cluster\n\u003e and configuration to use this module. Please see the [v3 to v4 migration path](./docs/migration-v3-v4.md) for more information.\n\u003e Release `2.0.0` (previously released as version `0.45.0`) contains some changes that,\n\u003e if applied to a cluster created with an earlier version of this module,\n\u003e could result in your existing EKS cluster being replaced (destroyed and recreated).\n\u003e To prevent this, follow the instructions in the [v1 to v2 migration path](./docs/migration-v1-v2.md).\n\n\u003e [!NOTE]\n\u003e Prior to v4 of this module, AWS did not provide an API to manage access to the EKS cluster,\n\u003e causing numerous challenges. With v4 of this module, it exclusively uses the AWS API, resolving\n\u003e many issues you may read about that had affected prior versions. See the version 2 README and release notes\n\u003e for more information on the challenges and workarounds that were required prior to v3.\n\n## EKS Auto Mode\n\nThis module supports [EKS Auto Mode](https://docs.aws.amazon.com/eks/latest/userguide/automode.html) (GA December 2024),\nwhich delegates compute, networking, and storage management to AWS. Enable it using the `auto_mode_compute_config`,\n`auto_mode_storage_config`, and `auto_mode_elastic_load_balancing` variables.\n\n### Enabling Auto Mode\n\n```hcl\nmodule \"eks_cluster\" {\n  source  = \"cloudposse/eks-cluster/aws\"\n  # version = \"...\"\n\n  auto_mode_compute_config = {\n    enabled       = true\n    node_pools    = [\"general-purpose\", \"system\"]\n    node_role_arn = aws_iam_role.auto_mode_node.arn\n  }\n\n  auto_mode_storage_config = {\n    block_storage = {\n      enabled = true\n    }\n  }\n\n  auto_mode_elastic_load_balancing = {\n    enabled = true\n  }\n\n  # ... other configuration\n}\n```\n\nWhen Auto Mode is enabled, this module automatically:\n- Sets `bootstrap_self_managed_addons = false` (unless explicitly overridden)\n- Adds `sts:TagSession` to the cluster IAM role trust policy\n- Attaches 4 additional IAM policies to the cluster role: `AmazonEKSComputePolicy`, `AmazonEKSBlockStoragePolicy`,\n  `AmazonEKSLoadBalancingPolicy`, and `AmazonEKSNetworkingPolicy`\n\n### Auto Mode Managed Add-ons\n\nWhen Auto Mode is enabled, AWS manages the following add-ons automatically:\n\n| Add-on | Variable | What AWS Manages |\n|--------|----------|-----------------|\n| **Compute** | `auto_mode_compute_config` | Node provisioning via managed Karpenter |\n| **Storage** | `auto_mode_storage_config` | EBS volumes via `ebs.csi.eks.amazonaws.com` |\n| **Networking** | `auto_mode_elastic_load_balancing` | ALB/NLB for Services and Ingress |\n\n### Important Notes\n\n- Requires AWS provider `\u003e= 5.79.0` and Kubernetes `\u003e= 1.29`\n- Auto Mode manages `vpc-cni`, `kube-proxy`, `coredns`, and `aws-ebs-csi-driver` add-ons automatically.\n  Do not include these in the `addons` variable when Auto Mode is enabled.\n- Auto Mode nodes are Bottlerocket-only, immutable, with no SSH/IMDS access\n- Nodes have a 21-day maximum lifetime and are automatically rotated\n- The `node_role_arn` in `auto_mode_compute_config` must be an IAM role with\n  `AmazonEKSWorkerNodeMinimalPolicy` and `AmazonEC2ContainerRegistryPullOnly` attached\n\n### Cluster Version Upgrades\n\nWith Auto Mode, Kubernetes version upgrades are simplified:\n1. Bump `kubernetes_version` and apply -- control plane upgrades in place\n2. Managed Karpenter detects version drift and automatically replaces nodes\n3. Auto Mode-managed add-ons are automatically upgraded to compatible versions\n\n\u003e [!IMPORTANT]\n\u003e In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation\n\u003e and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version\n\u003e you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic\n\u003e approach for updating versions to avoid unexpected changes.\n\n\n\n\n\n\n\n\n\u003c!-- markdownlint-disable --\u003e\n## Requirements\n\n| Name | Version |\n|------|---------|\n| \u003ca name=\"requirement_terraform\"\u003e\u003c/a\u003e [terraform](#requirement\\_terraform) | \u003e= 1.3.0 |\n| \u003ca name=\"requirement_aws\"\u003e\u003c/a\u003e [aws](#requirement\\_aws) | \u003e= 6.25.0 |\n| \u003ca name=\"requirement_tls\"\u003e\u003c/a\u003e [tls](#requirement\\_tls) | \u003e= 3.1.0, != 4.0.0 |\n\n## Providers\n\n| Name | Version |\n|------|---------|\n| \u003ca name=\"provider_aws\"\u003e\u003c/a\u003e [aws](#provider\\_aws) | \u003e= 6.25.0 |\n| \u003ca name=\"provider_tls\"\u003e\u003c/a\u003e [tls](#provider\\_tls) | \u003e= 3.1.0, != 4.0.0 |\n\n## Modules\n\n| Name | Source | Version |\n|------|--------|---------|\n| \u003ca name=\"module_capability_label\"\u003e\u003c/a\u003e [capability\\_label](#module\\_capability\\_label) | cloudposse/label/null | 0.25.0 |\n| \u003ca name=\"module_label\"\u003e\u003c/a\u003e [label](#module\\_label) | cloudposse/label/null | 0.25.0 |\n| \u003ca name=\"module_this\"\u003e\u003c/a\u003e [this](#module\\_this) | cloudposse/label/null | 0.25.0 |\n\n## Resources\n\n| Name | Type |\n|------|------|\n| [aws_cloudwatch_log_group.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group) | resource |\n| [aws_eks_access_entry.linux](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_entry) | resource |\n| [aws_eks_access_entry.map](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_entry) | resource |\n| [aws_eks_access_entry.standard](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_entry) | resource |\n| [aws_eks_access_entry.windows](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_entry) | resource |\n| [aws_eks_access_policy_association.list](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_policy_association) | resource |\n| [aws_eks_access_policy_association.map](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_access_policy_association) | resource |\n| [aws_eks_addon.cluster](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_addon) | resource |\n| [aws_eks_capability.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_capability) | resource |\n| [aws_eks_cluster.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_cluster) | resource |\n| [aws_iam_openid_connect_provider.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_openid_connect_provider) | resource |\n| [aws_iam_policy.cluster_elb_service_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_policy) | resource |\n| [aws_iam_role.capability](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role) | resource |\n| [aws_iam_role.default](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role) | resource |\n| [aws_iam_role_policy_attachment.amazon_eks_cluster_policy](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role_policy_attachment) | resource |\n| [aws_iam_role_policy_attachment.amazon_eks_service_policy](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role_policy_attachment) | resource |\n| [aws_iam_role_policy_attachment.auto_mode](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role_policy_attachment) | resource |\n| [aws_iam_role_policy_attachment.cluster_elb_service_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role_policy_attachment) | resource |\n| [aws_kms_alias.cluster](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_alias) | resource |\n| [aws_kms_key.cluster](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/kms_key) | resource |\n| [aws_vpc_security_group_ingress_rule.custom_ingress_rules](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_security_group_ingress_rule) | resource |\n| [aws_vpc_security_group_ingress_rule.managed_ingress_cidr_blocks](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_security_group_ingress_rule) | resource |\n| [aws_vpc_security_group_ingress_rule.managed_ingress_security_groups](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc_security_group_ingress_rule) | resource |\n| [aws_iam_policy_document.assume_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |\n| [aws_iam_policy_document.capability_assume_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |\n| [aws_iam_policy_document.cluster_elb_service_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document) | data source |\n| [aws_partition.current](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/partition) | data source |\n| [tls_certificate.cluster](https://registry.terraform.io/providers/hashicorp/tls/latest/docs/data-sources/certificate) | data source |\n\n## Inputs\n\n| Name | Description | Type | Default | Required |\n|------|-------------|------|---------|:--------:|\n| \u003ca name=\"input_access_config\"\u003e\u003c/a\u003e [access\\_config](#input\\_access\\_config) | Access configuration for the EKS cluster. | \u003cpre\u003eobject({\u003cbr/\u003e    authentication_mode                         = optional(string, \"API\")\u003cbr/\u003e    bootstrap_cluster_creator_admin_permissions = optional(bool, false)\u003cbr/\u003e  })\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_access_entries\"\u003e\u003c/a\u003e [access\\_entries](#input\\_access\\_entries) | List of IAM principles to allow to access the EKS cluster.\u003cbr/\u003eIt is recommended to use the default `user_name` because the default includes\u003cbr/\u003ethe IAM role or user name and the session name for assumed roles.\u003cbr/\u003eUse when Principal ARN is not known at plan time. | \u003cpre\u003elist(object({\u003cbr/\u003e    principal_arn     = string\u003cbr/\u003e    user_name         = optional(string, null)\u003cbr/\u003e    kubernetes_groups = optional(list(string), null)\u003cbr/\u003e  }))\u003c/pre\u003e | `[]` | no |\n| \u003ca name=\"input_access_entries_for_nodes\"\u003e\u003c/a\u003e [access\\_entries\\_for\\_nodes](#input\\_access\\_entries\\_for\\_nodes) | Map of list of IAM roles for the EKS non-managed worker nodes.\u003cbr/\u003eThe map key is the node type, either `EC2_LINUX` or `EC2_WINDOWS`,\u003cbr/\u003eand the list contains the IAM roles of the nodes of that type.\u003cbr/\u003eThere is no need for or utility in creating Fargate access entries, as those\u003cbr/\u003eare always created automatically by AWS, just as with managed nodes.\u003cbr/\u003eUse when Principal ARN is not known at plan time. | `map(list(string))` | `{}` | no |\n| \u003ca name=\"input_access_entry_map\"\u003e\u003c/a\u003e [access\\_entry\\_map](#input\\_access\\_entry\\_map) | Map of IAM Principal ARNs to access configuration.\u003cbr/\u003ePreferred over other inputs as this configuration remains stable\u003cbr/\u003ewhen elements are added or removed, but it requires that the Principal ARNs\u003cbr/\u003eand Policy ARNs are known at plan time.\u003cbr/\u003eCan be used along with other `access_*` inputs, but do not duplicate entries.\u003cbr/\u003eMap `access_policy_associations` keys are policy ARNs, policy\u003cbr/\u003efull name (AmazonEKSViewPolicy), or short name (View).\u003cbr/\u003eIt is recommended to use the default `user_name` because the default includes\u003cbr/\u003eIAM role or user name and the session name for assumed roles.\u003cbr/\u003eAs a special case in support of backwards compatibility, membership in the\u003cbr/\u003e`system:masters` group is is translated to an association with the ClusterAdmin policy.\u003cbr/\u003eIn all other cases, including any `system:*` group in `kubernetes_groups` is prohibited. | \u003cpre\u003emap(object({\u003cbr/\u003e    # key is principal_arn\u003cbr/\u003e    user_name = optional(string)\u003cbr/\u003e    # Cannot assign \"system:*\" groups to IAM users, use ClusterAdmin and Admin instead\u003cbr/\u003e    kubernetes_groups = optional(list(string), [])\u003cbr/\u003e    type              = optional(string, \"STANDARD\")\u003cbr/\u003e    access_policy_associations = optional(map(object({\u003cbr/\u003e      # key is policy_arn or policy_name\u003cbr/\u003e      access_scope = optional(object({\u003cbr/\u003e        type       = optional(string, \"cluster\")\u003cbr/\u003e        namespaces = optional(list(string))\u003cbr/\u003e      }), {}) # access_scope\u003cbr/\u003e    })), {})  # access_policy_associations\u003cbr/\u003e  }))\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_access_policy_associations\"\u003e\u003c/a\u003e [access\\_policy\\_associations](#input\\_access\\_policy\\_associations) | List of AWS managed EKS access policies to associate with IAM principles.\u003cbr/\u003eUse when Principal ARN or Policy ARN is not known at plan time.\u003cbr/\u003e`policy_arn` can be the full ARN, the full name (AmazonEKSViewPolicy) or short name (View). | \u003cpre\u003elist(object({\u003cbr/\u003e    principal_arn = string\u003cbr/\u003e    policy_arn    = string\u003cbr/\u003e    access_scope = optional(object({\u003cbr/\u003e      type       = optional(string, \"cluster\")\u003cbr/\u003e      namespaces = optional(list(string))\u003cbr/\u003e    }), {})\u003cbr/\u003e  }))\u003c/pre\u003e | `[]` | no |\n| \u003ca name=\"input_additional_tag_map\"\u003e\u003c/a\u003e [additional\\_tag\\_map](#input\\_additional\\_tag\\_map) | Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`.\u003cbr/\u003eThis is for some rare cases where resources want additional configuration of tags\u003cbr/\u003eand therefore take a list of maps with tag key, value, and additional configuration. | `map(string)` | `{}` | no |\n| \u003ca name=\"input_addons\"\u003e\u003c/a\u003e [addons](#input\\_addons) | Manages [`aws_eks_addon`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eks_addon) resources.\u003cbr/\u003eNote: `resolve_conflicts` is deprecated. If `resolve_conflicts` is set and\u003cbr/\u003e`resolve_conflicts_on_create` or `resolve_conflicts_on_update` is not set,\u003cbr/\u003e`resolve_conflicts` will be used instead. If `resolve_conflicts_on_create` is\u003cbr/\u003enot set and `resolve_conflicts` is `PRESERVE`, `resolve_conflicts_on_create`\u003cbr/\u003ewill be set to `NONE`.\u003cbr/\u003eIf `additional_tags` are specified, they are added to the standard resource tags. | \u003cpre\u003elist(object({\u003cbr/\u003e    addon_name           = string\u003cbr/\u003e    addon_version        = optional(string, null)\u003cbr/\u003e    configuration_values = optional(string, null)\u003cbr/\u003e    # resolve_conflicts is deprecated, but we keep it for backwards compatibility\u003cbr/\u003e    # and because if not declared, Terraform will silently ignore it.\u003cbr/\u003e    resolve_conflicts           = optional(string, null)\u003cbr/\u003e    resolve_conflicts_on_create = optional(string, null)\u003cbr/\u003e    resolve_conflicts_on_update = optional(string, null)\u003cbr/\u003e    service_account_role_arn    = optional(string, null)\u003cbr/\u003e    pod_identity_association    = optional(map(string), {})\u003cbr/\u003e    create_timeout              = optional(string, null)\u003cbr/\u003e    update_timeout              = optional(string, null)\u003cbr/\u003e    delete_timeout              = optional(string, null)\u003cbr/\u003e    additional_tags             = optional(map(string), {})\u003cbr/\u003e  }))\u003c/pre\u003e | `[]` | no |\n| \u003ca name=\"input_addons_depends_on\"\u003e\u003c/a\u003e [addons\\_depends\\_on](#input\\_addons\\_depends\\_on) | If provided, all addons will depend on this object, and therefore not be installed until this object is finalized.\u003cbr/\u003eThis is useful if you want to ensure that addons are not applied before some other condition is met, e.g. node groups are created.\u003cbr/\u003eSee [issue #170](https://github.com/cloudposse/terraform-aws-eks-cluster/issues/170) for more details. | `any` | `null` | no |\n| \u003ca name=\"input_allowed_cidr_blocks\"\u003e\u003c/a\u003e [allowed\\_cidr\\_blocks](#input\\_allowed\\_cidr\\_blocks) | A list of IPv4 CIDRs to allow access to the cluster.\u003cbr/\u003eThe length of this list must be known at \"plan\" time. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_allowed_security_group_ids\"\u003e\u003c/a\u003e [allowed\\_security\\_group\\_ids](#input\\_allowed\\_security\\_group\\_ids) | A list of IDs of Security Groups to allow access to the cluster. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_associated_security_group_ids\"\u003e\u003c/a\u003e [associated\\_security\\_group\\_ids](#input\\_associated\\_security\\_group\\_ids) | A list of IDs of Security Groups to associate the cluster with.\u003cbr/\u003eThese security groups will not be modified. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_attributes\"\u003e\u003c/a\u003e [attributes](#input\\_attributes) | ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`,\u003cbr/\u003ein the order they appear in the list. New attributes are appended to the\u003cbr/\u003eend of the list. The elements of the list are joined by the `delimiter`\u003cbr/\u003eand treated as a single ID element. | `list(string)` | `[]` | no |\n| \u003ca name=\"input_auto_mode_compute_config\"\u003e\u003c/a\u003e [auto\\_mode\\_compute\\_config](#input\\_auto\\_mode\\_compute\\_config) | EKS Auto Mode compute configuration. When enabled, AWS manages node\u003cbr/\u003eprovisioning via managed Karpenter. | \u003cpre\u003eobject({\u003cbr/\u003e    enabled       = optional(bool, false)\u003cbr/\u003e    node_pools    = optional(set(string), [\"general-purpose\", \"system\"])\u003cbr/\u003e    node_role_arn = optional(string, null)\u003cbr/\u003e  })\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_auto_mode_elastic_load_balancing\"\u003e\u003c/a\u003e [auto\\_mode\\_elastic\\_load\\_balancing](#input\\_auto\\_mode\\_elastic\\_load\\_balancing) | EKS Auto Mode elastic load balancing configuration. When enabled,\u003cbr/\u003eAWS manages ALB/NLB creation for Services and Ingress resources. | \u003cpre\u003eobject({\u003cbr/\u003e    enabled = optional(bool, false)\u003cbr/\u003e  })\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_auto_mode_storage_config\"\u003e\u003c/a\u003e [auto\\_mode\\_storage\\_config](#input\\_auto\\_mode\\_storage\\_config) | EKS Auto Mode storage configuration. When block\\_storage is enabled,\u003cbr/\u003eAWS manages EBS volumes via the ebs.csi.eks.amazonaws.com provisioner. | \u003cpre\u003eobject({\u003cbr/\u003e    block_storage = optional(object({\u003cbr/\u003e      enabled = optional(bool, false)\u003cbr/\u003e    }), {})\u003cbr/\u003e  })\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_bootstrap_self_managed_addons_enabled\"\u003e\u003c/a\u003e [bootstrap\\_self\\_managed\\_addons\\_enabled](#input\\_bootstrap\\_self\\_managed\\_addons\\_enabled) | Manages bootstrap of default networking addons after cluster has been created. Must be false when Auto Mode is enabled. Changing this forces cluster recreation. | `bool` | `null` | no |\n| \u003ca name=\"input_capabilities\"\u003e\u003c/a\u003e [capabilities](#input\\_capabilities) | Map of EKS Capabilities to enable on the cluster. Each key is the capability\u003cbr/\u003ename (must be unique within the cluster). Supported types: ACK, ARGOCD, KRO.\u003cbr/\u003e\u003cbr/\u003eWhen `create_iam_role` is true (default) and `role_arn` is null, an IAM\u003cbr/\u003erole with a trust policy for `capabilities.eks.amazonaws.com` is\u003cbr/\u003eautomatically created. Set `create_iam_role = false` and provide `role_arn`\u003cbr/\u003ewhen the calling module creates its own IAM roles (avoids plan-time unknowns).\u003cbr/\u003e\u003cbr/\u003eThe `configuration` block is only applicable to ARGOCD capabilities.\u003cbr/\u003eACK and KRO do not currently support configuration. | \u003cpre\u003emap(object({\u003cbr/\u003e    enabled                   = optional(bool, true)\u003cbr/\u003e    type                      = string # ACK, ARGOCD, KRO\u003cbr/\u003e    create_iam_role           = optional(bool, true)\u003cbr/\u003e    role_arn                  = optional(string, null)\u003cbr/\u003e    delete_propagation_policy = optional(string, \"RETAIN\")\u003cbr/\u003e    configuration = optional(object({\u003cbr/\u003e      argo_cd = optional(object({\u003cbr/\u003e        namespace = optional(string, \"argocd\")\u003cbr/\u003e        aws_idc = optional(object({\u003cbr/\u003e          idc_instance_arn = string\u003cbr/\u003e          idc_region       = optional(string, null)\u003cbr/\u003e        }), null)\u003cbr/\u003e        network_access = optional(object({\u003cbr/\u003e          vpce_ids = optional(list(string), [])\u003cbr/\u003e        }), null)\u003cbr/\u003e        rbac_role_mapping = optional(list(object({\u003cbr/\u003e          role = string # ADMIN, EDITOR, VIEWER\u003cbr/\u003e          identity = list(object({\u003cbr/\u003e            id   = string\u003cbr/\u003e            type = string # SSO_USER, SSO_GROUP\u003cbr/\u003e          }))\u003cbr/\u003e        })), [])\u003cbr/\u003e      }), null)\u003cbr/\u003e    }), null)\u003cbr/\u003e    create_timeout = optional(string, null)\u003cbr/\u003e    update_timeout = optional(string, null)\u003cbr/\u003e    delete_timeout = optional(string, null)\u003cbr/\u003e  }))\u003c/pre\u003e | `{}` | no |\n| \u003ca name=\"input_cloudwatch_log_group_class\"\u003e\u003c/a\u003e [cloudwatch\\_log\\_group\\_class](#input\\_cloudwatch\\_log\\_group\\_class) | Specified the log class of the log group. Possible values are: `STANDARD` or `INFREQUENT_ACCESS` | `string` | `null` | no |\n| \u003ca name=\"input_cloudwatch_log_group_kms_key_id\"\u003e\u003c/a\u003e [cloudwatch\\_log\\_group\\_kms\\_key\\_id](#input\\_cloudwatch\\_log\\_group\\_kms\\_key\\_id) | If provided, the KMS Key ID to use to encrypt AWS CloudWatch logs | `string` | `null` | no |\n| \u003ca name=\"input_cluster_attributes\"\u003e\u003c/a\u003e [cluster\\_attributes](#input\\_cluster\\_attributes) | Override label module default cluster attributes | `list(string)` | \u003cpre\u003e[\u003cbr/\u003e  \"cluster\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_cluster_depends_on\"\u003e\u003c/a\u003e [cluster\\_depends\\_on](#input\\_cluster\\_depends\\_on) | If provided, the EKS will depend on this object, and therefore not be created until this object is finalized.\u003cbr/\u003eThis is useful if you want to ensure that the cluster is not created before some other condition is met, e.g. VPNs into the subnet are created. | `any` | `null` | no |\n| \u003ca name=\"input_cluster_encryption_config_enabled\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_enabled](#input\\_cluster\\_encryption\\_config\\_enabled) | Set to `true` to enable Cluster Encryption Configuration | `bool` | `true` | no |\n| \u003ca name=\"input_cluster_encryption_config_kms_key_deletion_window_in_days\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_kms\\_key\\_deletion\\_window\\_in\\_days](#input\\_cluster\\_encryption\\_config\\_kms\\_key\\_deletion\\_window\\_in\\_days) | Cluster Encryption Config KMS Key Resource argument - key deletion windows in days post destruction | `number` | `10` | no |\n| \u003ca name=\"input_cluster_encryption_config_kms_key_enable_key_rotation\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_kms\\_key\\_enable\\_key\\_rotation](#input\\_cluster\\_encryption\\_config\\_kms\\_key\\_enable\\_key\\_rotation) | Cluster Encryption Config KMS Key Resource argument - enable kms key rotation | `bool` | `true` | no |\n| \u003ca name=\"input_cluster_encryption_config_kms_key_id\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_kms\\_key\\_id](#input\\_cluster\\_encryption\\_config\\_kms\\_key\\_id) | KMS Key ID to use for cluster encryption config | `string` | `\"\"` | no |\n| \u003ca name=\"input_cluster_encryption_config_kms_key_policy\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_kms\\_key\\_policy](#input\\_cluster\\_encryption\\_config\\_kms\\_key\\_policy) | Cluster Encryption Config KMS Key Resource argument - key policy | `string` | `null` | no |\n| \u003ca name=\"input_cluster_encryption_config_resources\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_resources](#input\\_cluster\\_encryption\\_config\\_resources) | Cluster Encryption Config Resources to encrypt, e.g. ['secrets'] | `list(any)` | \u003cpre\u003e[\u003cbr/\u003e  \"secrets\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_cluster_log_retention_period\"\u003e\u003c/a\u003e [cluster\\_log\\_retention\\_period](#input\\_cluster\\_log\\_retention\\_period) | Number of days to retain cluster logs. Requires `enabled_cluster_log_types` to be set. See https://docs.aws.amazon.com/en_us/eks/latest/userguide/control-plane-logs.html. | `number` | `0` | no |\n| \u003ca name=\"input_context\"\u003e\u003c/a\u003e [context](#input\\_context) | Single object for setting entire context at once.\u003cbr/\u003eSee description of individual variables for details.\u003cbr/\u003eLeave string and numeric variables as `null` to use default value.\u003cbr/\u003eIndividual variable settings (non-null) override settings in context object,\u003cbr/\u003eexcept for attributes, tags, and additional\\_tag\\_map, which are merged. | `any` | \u003cpre\u003e{\u003cbr/\u003e  \"additional_tag_map\": {},\u003cbr/\u003e  \"attributes\": [],\u003cbr/\u003e  \"delimiter\": null,\u003cbr/\u003e  \"descriptor_formats\": {},\u003cbr/\u003e  \"enabled\": true,\u003cbr/\u003e  \"environment\": null,\u003cbr/\u003e  \"id_length_limit\": null,\u003cbr/\u003e  \"label_key_case\": null,\u003cbr/\u003e  \"label_order\": [],\u003cbr/\u003e  \"label_value_case\": null,\u003cbr/\u003e  \"labels_as_tags\": [\u003cbr/\u003e    \"unset\"\u003cbr/\u003e  ],\u003cbr/\u003e  \"name\": null,\u003cbr/\u003e  \"namespace\": null,\u003cbr/\u003e  \"regex_replace_chars\": null,\u003cbr/\u003e  \"stage\": null,\u003cbr/\u003e  \"tags\": {},\u003cbr/\u003e  \"tenant\": null\u003cbr/\u003e}\u003c/pre\u003e | no |\n| \u003ca name=\"input_create_eks_service_role\"\u003e\u003c/a\u003e [create\\_eks\\_service\\_role](#input\\_create\\_eks\\_service\\_role) | Set `false` to use existing `eks_cluster_service_role_arn` instead of creating one | `bool` | `true` | no |\n| \u003ca name=\"input_custom_ingress_rules\"\u003e\u003c/a\u003e [custom\\_ingress\\_rules](#input\\_custom\\_ingress\\_rules) | A List of Objects, which are custom security group rules that | \u003cpre\u003elist(object({\u003cbr/\u003e    description              = string\u003cbr/\u003e    from_port                = number\u003cbr/\u003e    to_port                  = number\u003cbr/\u003e    protocol                 = string\u003cbr/\u003e    source_security_group_id = string\u003cbr/\u003e  }))\u003c/pre\u003e | `[]` | no |\n| \u003ca name=\"input_delimiter\"\u003e\u003c/a\u003e [delimiter](#input\\_delimiter) | Delimiter to be used between ID elements.\u003cbr/\u003eDefaults to `-` (hyphen). Set to `\"\"` to use no delimiter at all. | `string` | `null` | no |\n| \u003ca name=\"input_descriptor_formats\"\u003e\u003c/a\u003e [descriptor\\_formats](#input\\_descriptor\\_formats) | Describe additional descriptors to be output in the `descriptors` output map.\u003cbr/\u003eMap of maps. Keys are names of descriptors. Values are maps of the form\u003cbr/\u003e`{\u003cbr/\u003e   format = string\u003cbr/\u003e   labels = list(string)\u003cbr/\u003e}`\u003cbr/\u003e(Type is `any` so the map values can later be enhanced to provide additional options.)\u003cbr/\u003e`format` is a Terraform format string to be passed to the `format()` function.\u003cbr/\u003e`labels` is a list of labels, in order, to pass to `format()` function.\u003cbr/\u003eLabel values will be normalized before being passed to `format()` so they will be\u003cbr/\u003eidentical to how they appear in `id`.\u003cbr/\u003eDefault is `{}` (`descriptors` output will be empty). | `any` | `{}` | no |\n| \u003ca name=\"input_eks_cluster_service_role_arn\"\u003e\u003c/a\u003e [eks\\_cluster\\_service\\_role\\_arn](#input\\_eks\\_cluster\\_service\\_role\\_arn) | The ARN of an IAM role for the EKS cluster to use that provides permissions\u003cbr/\u003efor the Kubernetes control plane to perform needed AWS API operations.\u003cbr/\u003eRequired if `create_eks_service_role` is `false`, ignored otherwise. | `string` | `null` | no |\n| \u003ca name=\"input_enabled\"\u003e\u003c/a\u003e [enabled](#input\\_enabled) | Set to false to prevent the module from creating any resources | `bool` | `null` | no |\n| \u003ca name=\"input_enabled_cluster_log_types\"\u003e\u003c/a\u003e [enabled\\_cluster\\_log\\_types](#input\\_enabled\\_cluster\\_log\\_types) | A list of the desired control plane logging to enable. For more information, see https://docs.aws.amazon.com/en_us/eks/latest/userguide/control-plane-logs.html. Possible values [`api`, `audit`, `authenticator`, `controllerManager`, `scheduler`] | `list(string)` | `[]` | no |\n| \u003ca name=\"input_endpoint_private_access\"\u003e\u003c/a\u003e [endpoint\\_private\\_access](#input\\_endpoint\\_private\\_access) | Indicates whether or not the Amazon EKS private API server endpoint is enabled. Default to AWS EKS resource and it is false | `bool` | `false` | no |\n| \u003ca name=\"input_endpoint_public_access\"\u003e\u003c/a\u003e [endpoint\\_public\\_access](#input\\_endpoint\\_public\\_access) | Indicates whether or not the Amazon EKS public API server endpoint is enabled. Default to AWS EKS resource and it is true | `bool` | `true` | no |\n| \u003ca name=\"input_environment\"\u003e\u003c/a\u003e [environment](#input\\_environment) | ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT' | `string` | `null` | no |\n| \u003ca name=\"input_id_length_limit\"\u003e\u003c/a\u003e [id\\_length\\_limit](#input\\_id\\_length\\_limit) | Limit `id` to this many characters (minimum 6).\u003cbr/\u003eSet to `0` for unlimited length.\u003cbr/\u003eSet to `null` for keep the existing setting, which defaults to `0`.\u003cbr/\u003eDoes not affect `id_full`. | `number` | `null` | no |\n| \u003ca name=\"input_kubernetes_network_ipv6_enabled\"\u003e\u003c/a\u003e [kubernetes\\_network\\_ipv6\\_enabled](#input\\_kubernetes\\_network\\_ipv6\\_enabled) | Set true to use IPv6 addresses for Kubernetes pods and services | `bool` | `false` | no |\n| \u003ca name=\"input_kubernetes_version\"\u003e\u003c/a\u003e [kubernetes\\_version](#input\\_kubernetes\\_version) | Desired Kubernetes master version. If you do not specify a value, the latest available version is used | `string` | `\"1.21\"` | no |\n| \u003ca name=\"input_label_key_case\"\u003e\u003c/a\u003e [label\\_key\\_case](#input\\_label\\_key\\_case) | Controls the letter case of the `tags` keys (label names) for tags generated by this module.\u003cbr/\u003eDoes not affect keys of tags passed in via the `tags` input.\u003cbr/\u003ePossible values: `lower`, `title`, `upper`.\u003cbr/\u003eDefault value: `title`. | `string` | `null` | no |\n| \u003ca name=\"input_label_order\"\u003e\u003c/a\u003e [label\\_order](#input\\_label\\_order) | The order in which the labels (ID elements) appear in the `id`.\u003cbr/\u003eDefaults to [\"namespace\", \"environment\", \"stage\", \"name\", \"attributes\"].\u003cbr/\u003eYou can omit any of the 6 labels (\"tenant\" is the 6th), but at least one must be present. | `list(string)` | `null` | no |\n| \u003ca name=\"input_label_value_case\"\u003e\u003c/a\u003e [label\\_value\\_case](#input\\_label\\_value\\_case) | Controls the letter case of ID elements (labels) as included in `id`,\u003cbr/\u003eset as tag values, and output by this module individually.\u003cbr/\u003eDoes not affect values of tags passed in via the `tags` input.\u003cbr/\u003ePossible values: `lower`, `title`, `upper` and `none` (no transformation).\u003cbr/\u003eSet this to `title` and set `delimiter` to `\"\"` to yield Pascal Case IDs.\u003cbr/\u003eDefault value: `lower`. | `string` | `null` | no |\n| \u003ca name=\"input_labels_as_tags\"\u003e\u003c/a\u003e [labels\\_as\\_tags](#input\\_labels\\_as\\_tags) | Set of labels (ID elements) to include as tags in the `tags` output.\u003cbr/\u003eDefault is to include all labels.\u003cbr/\u003eTags with empty values will not be included in the `tags` output.\u003cbr/\u003eSet to `[]` to suppress all generated tags.\u003cbr/\u003e**Notes:**\u003cbr/\u003e  The value of the `name` tag, if included, will be the `id`, not the `name`.\u003cbr/\u003e  Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be\u003cbr/\u003e  changed in later chained modules. Attempts to change it will be silently ignored. | `set(string)` | \u003cpre\u003e[\u003cbr/\u003e  \"default\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_managed_security_group_rules_enabled\"\u003e\u003c/a\u003e [managed\\_security\\_group\\_rules\\_enabled](#input\\_managed\\_security\\_group\\_rules\\_enabled) | Flag to enable/disable the ingress and egress rules for the EKS managed Security Group | `bool` | `true` | no |\n| \u003ca name=\"input_name\"\u003e\u003c/a\u003e [name](#input\\_name) | ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.\u003cbr/\u003eThis is the only ID element not also included as a `tag`.\u003cbr/\u003eThe \"name\" tag is set to the full `id` string. There is no tag with the value of the `name` input. | `string` | `null` | no |\n| \u003ca name=\"input_namespace\"\u003e\u003c/a\u003e [namespace](#input\\_namespace) | ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique | `string` | `null` | no |\n| \u003ca name=\"input_oidc_provider_enabled\"\u003e\u003c/a\u003e [oidc\\_provider\\_enabled](#input\\_oidc\\_provider\\_enabled) | Create an IAM OIDC identity provider for the cluster, then you can create IAM roles to associate with a\u003cbr/\u003eservice account in the cluster, instead of using kiam or kube2iam. For more information,\u003cbr/\u003esee [EKS User Guide](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html). | `bool` | `false` | no |\n| \u003ca name=\"input_permissions_boundary\"\u003e\u003c/a\u003e [permissions\\_boundary](#input\\_permissions\\_boundary) | If provided, all IAM roles will be created with this permissions boundary attached | `string` | `null` | no |\n| \u003ca name=\"input_public_access_cidrs\"\u003e\u003c/a\u003e [public\\_access\\_cidrs](#input\\_public\\_access\\_cidrs) | Indicates which CIDR blocks can access the Amazon EKS public API server endpoint when enabled. EKS defaults this to a list with 0.0.0.0/0. | `list(string)` | \u003cpre\u003e[\u003cbr/\u003e  \"0.0.0.0/0\"\u003cbr/\u003e]\u003c/pre\u003e | no |\n| \u003ca name=\"input_regex_replace_chars\"\u003e\u003c/a\u003e [regex\\_replace\\_chars](#input\\_regex\\_replace\\_chars) | Terraform regular expression (regex) string.\u003cbr/\u003eCharacters matching the regex will be removed from the ID elements.\u003cbr/\u003eIf not set, `\"/[^a-zA-Z0-9-]/\"` is used to remove all characters other than hyphens, letters and digits. | `string` | `null` | no |\n| \u003ca name=\"input_region\"\u003e\u003c/a\u003e [region](#input\\_region) | OBSOLETE (not needed): AWS Region | `string` | `null` | no |\n| \u003ca name=\"input_remote_network_config\"\u003e\u003c/a\u003e [remote\\_network\\_config](#input\\_remote\\_network\\_config) | Configuration block for the cluster remote network configuration | \u003cpre\u003eobject({\u003cbr/\u003e    remote_node_networks_cidrs = list(string)\u003cbr/\u003e    remote_pod_networks_cidrs  = optional(list(string))\u003cbr/\u003e  })\u003c/pre\u003e | `null` | no |\n| \u003ca name=\"input_service_ipv4_cidr\"\u003e\u003c/a\u003e [service\\_ipv4\\_cidr](#input\\_service\\_ipv4\\_cidr) | The CIDR block to assign Kubernetes service IP addresses from.\u003cbr/\u003eYou can only specify a custom CIDR block when you create a cluster, changing this value will force a new cluster to be created. | `string` | `null` | no |\n| \u003ca name=\"input_stage\"\u003e\u003c/a\u003e [stage](#input\\_stage) | ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release' | `string` | `null` | no |\n| \u003ca name=\"input_subnet_ids\"\u003e\u003c/a\u003e [subnet\\_ids](#input\\_subnet\\_ids) | A list of subnet IDs to launch the cluster in | `list(string)` | n/a | yes |\n| \u003ca name=\"input_tags\"\u003e\u003c/a\u003e [tags](#input\\_tags) | Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`).\u003cbr/\u003eNeither the tag keys nor the tag values will be modified by this module. | `map(string)` | `{}` | no |\n| \u003ca name=\"input_tenant\"\u003e\u003c/a\u003e [tenant](#input\\_tenant) | ID element \\_(Rarely used, not included by default)\\_. A customer identifier, indicating who this instance of a resource is for | `string` | `null` | no |\n| \u003ca name=\"input_upgrade_policy\"\u003e\u003c/a\u003e [upgrade\\_policy](#input\\_upgrade\\_policy) | Configuration block for the support policy to use for the cluster | \u003cpre\u003eobject({\u003cbr/\u003e    support_type = optional(string, null)\u003cbr/\u003e  })\u003c/pre\u003e | `null` | no |\n| \u003ca name=\"input_zonal_shift_config\"\u003e\u003c/a\u003e [zonal\\_shift\\_config](#input\\_zonal\\_shift\\_config) | Configuration block with zonal shift configuration for the cluster | \u003cpre\u003eobject({\u003cbr/\u003e    enabled = optional(bool, null)\u003cbr/\u003e  })\u003c/pre\u003e | `null` | no |\n\n## Outputs\n\n| Name | Description |\n|------|-------------|\n| \u003ca name=\"output_auto_mode_enabled\"\u003e\u003c/a\u003e [auto\\_mode\\_enabled](#output\\_auto\\_mode\\_enabled) | Whether EKS Auto Mode is enabled (all three capabilities: compute, storage, networking) |\n| \u003ca name=\"output_capabilities\"\u003e\u003c/a\u003e [capabilities](#output\\_capabilities) | Map of enabled EKS Capabilities with their ARNs and types |\n| \u003ca name=\"output_capability_role_arns\"\u003e\u003c/a\u003e [capability\\_role\\_arns](#output\\_capability\\_role\\_arns) | Map of auto-created capability IAM role ARNs |\n| \u003ca name=\"output_cloudwatch_log_group_kms_key_id\"\u003e\u003c/a\u003e [cloudwatch\\_log\\_group\\_kms\\_key\\_id](#output\\_cloudwatch\\_log\\_group\\_kms\\_key\\_id) | KMS Key ID to encrypt AWS CloudWatch logs |\n| \u003ca name=\"output_cloudwatch_log_group_name\"\u003e\u003c/a\u003e [cloudwatch\\_log\\_group\\_name](#output\\_cloudwatch\\_log\\_group\\_name) | The name of the log group created in cloudwatch where cluster logs are forwarded to if enabled |\n| \u003ca name=\"output_cluster_encryption_config_enabled\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_enabled](#output\\_cluster\\_encryption\\_config\\_enabled) | If true, Cluster Encryption Configuration is enabled |\n| \u003ca name=\"output_cluster_encryption_config_provider_key_alias\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_provider\\_key\\_alias](#output\\_cluster\\_encryption\\_config\\_provider\\_key\\_alias) | Cluster Encryption Config KMS Key Alias ARN |\n| \u003ca name=\"output_cluster_encryption_config_provider_key_arn\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_provider\\_key\\_arn](#output\\_cluster\\_encryption\\_config\\_provider\\_key\\_arn) | Cluster Encryption Config KMS Key ARN |\n| \u003ca name=\"output_cluster_encryption_config_resources\"\u003e\u003c/a\u003e [cluster\\_encryption\\_config\\_resources](#output\\_cluster\\_encryption\\_config\\_resources) | Cluster Encryption Config Resources |\n| \u003ca name=\"output_eks_addons_versions\"\u003e\u003c/a\u003e [eks\\_addons\\_versions](#output\\_eks\\_addons\\_versions) | Map of enabled EKS Addons names and versions |\n| \u003ca name=\"output_eks_cluster_arn\"\u003e\u003c/a\u003e [eks\\_cluster\\_arn](#output\\_eks\\_cluster\\_arn) | The Amazon Resource Name (ARN) of the cluster |\n| \u003ca name=\"output_eks_cluster_certificate_authority_data\"\u003e\u003c/a\u003e [eks\\_cluster\\_certificate\\_authority\\_data](#output\\_eks\\_cluster\\_certificate\\_authority\\_data) | The Kubernetes cluster certificate authority data |\n| \u003ca name=\"output_eks_cluster_endpoint\"\u003e\u003c/a\u003e [eks\\_cluster\\_endpoint](#output\\_eks\\_cluster\\_endpoint) | The endpoint for the Kubernetes API server |\n| \u003ca name=\"output_eks_cluster_id\"\u003e\u003c/a\u003e [eks\\_cluster\\_id](#output\\_eks\\_cluster\\_id) | The name of the cluster |\n| \u003ca name=\"output_eks_cluster_identity_oidc_issuer\"\u003e\u003c/a\u003e [eks\\_cluster\\_identity\\_oidc\\_issuer](#output\\_eks\\_cluster\\_identity\\_oidc\\_issuer) | The OIDC Identity issuer for the cluster |\n| \u003ca name=\"output_eks_cluster_identity_oidc_issuer_arn\"\u003e\u003c/a\u003e [eks\\_cluster\\_identity\\_oidc\\_issuer\\_arn](#output\\_eks\\_cluster\\_identity\\_oidc\\_issuer\\_arn) | The OIDC Identity issuer ARN for the cluster that can be used to associate IAM roles with a service account |\n| \u003ca name=\"output_eks_cluster_ipv4_service_cidr\"\u003e\u003c/a\u003e [eks\\_cluster\\_ipv4\\_service\\_cidr](#output\\_eks\\_cluster\\_ipv4\\_service\\_cidr) | The IPv4 CIDR block that Kubernetes pod and service IP addresses are assigned from\u003cbr/\u003eif `kubernetes_network_ipv6_enabled` is set to false. If set to true this output will be null. |\n| \u003ca name=\"output_eks_cluster_ipv6_service_cidr\"\u003e\u003c/a\u003e [eks\\_cluster\\_ipv6\\_service\\_cidr](#output\\_eks\\_cluster\\_ipv6\\_service\\_cidr) | The IPv6 CIDR block that Kubernetes pod and service IP addresses are assigned from\u003cbr/\u003eif `kubernetes_network_ipv6_enabled` is set to true. If set to false this output will be null. |\n| \u003ca name=\"output_eks_cluster_managed_security_group_id\"\u003e\u003c/a\u003e [eks\\_cluster\\_managed\\_security\\_group\\_id](#output\\_eks\\_cluster\\_managed\\_security\\_group\\_id) | Security Group ID that was created by EKS for the cluster.\u003cbr/\u003eEKS creates a Security Group and applies it to the ENI that are attached to EKS Control Plane master nodes and to any managed workloads. |\n| \u003ca name=\"output_eks_cluster_role_arn\"\u003e\u003c/a\u003e [eks\\_cluster\\_role\\_arn](#output\\_eks\\_cluster\\_role\\_arn) | ARN of the EKS cluster IAM role |\n| \u003ca name=\"output_eks_cluster_version\"\u003e\u003c/a\u003e [eks\\_cluster\\_version](#output\\_eks\\_cluster\\_version) | The Kubernetes server version of the cluster |\n\u003c!-- markdownlint-restore --\u003e\n\n\n\n\n\n\n\n## Related Projects\n\nCheck out these related projects.\n\n- [terraform-aws-components eks/clusters](https://github.com/cloudposse/terraform-aws-components/tree/main/modules/eks/cluster) - Cloud Posse's component (root module) using this module to provision an EKS cluster\n- [terraform-aws-components eks/karpenter and eks/karpenter-provisioner](https://github.com/cloudposse/terraform-aws-components/tree/main/modules/eks/karpenter) - Cloud Posse's components (root modules) deploying Karpenter to manage auto-scaling of EKS node groups\n- [terraform-aws-eks-workers](https://github.com/cloudposse/terraform-aws-eks-workers) - Terraform module to provision an AWS AutoScaling Group, IAM Role, and Security Group for EKS Workers\n- [terraform-aws-ec2-autoscale-group](https://github.com/cloudposse/terraform-aws-ec2-autoscale-group) - Terraform module to provision Auto Scaling Group and Launch Template on AWS\n- [terraform-aws-ecs-container-definition](https://github.com/cloudposse/terraform-aws-ecs-container-definition) - Terraform module to generate well-formed JSON documents (container definitions) that are passed to the  aws_ecs_task_definition Terraform resource\n- [terraform-aws-ecs-alb-service-task](https://github.com/cloudposse/terraform-aws-ecs-alb-service-task) - Terraform module which implements an ECS service which exposes a web service via ALB\n- [terraform-aws-ecs-web-app](https://github.com/cloudposse/terraform-aws-ecs-web-app) - Terraform module that implements a web app on ECS and supports autoscaling, CI/CD, monitoring, ALB integration, and much more\n- [terraform-aws-ecs-codepipeline](https://github.com/cloudposse/terraform-aws-ecs-codepipeline) - Terraform module for CI/CD with AWS Code Pipeline and Code Build for ECS\n- [terraform-aws-ecs-cloudwatch-autoscaling](https://github.com/cloudposse/terraform-aws-ecs-cloudwatch-autoscaling) - Terraform module to autoscale ECS Service based on CloudWatch metrics\n- [terraform-aws-ecs-cloudwatch-sns-alarms](https://github.com/cloudposse/terraform-aws-ecs-cloudwatch-sns-alarms) - Terraform module to create CloudWatch Alarms on ECS Service level metrics\n- [terraform-aws-ec2-instance](https://github.com/cloudposse/terraform-aws-ec2-instance) - Terraform module for providing a general purpose EC2 instance\n- [terraform-aws-ec2-instance-group](https://github.com/cloudposse/terraform-aws-ec2-instance-group) - Terraform module for provisioning multiple general purpose EC2 hosts for stateful applications\n\n\n\u003e [!TIP]\n\u003e #### Use Terraform Reference Architectures for AWS\n\u003e\n\u003e Use Cloud Posse's ready-to-go [terraform architecture blueprints](https://cloudposse.com/reference-architecture/) for AWS to get up and running quickly.\n\u003e\n\u003e ✅ We build it together with your team.\u003cbr/\u003e\n\u003e ✅ Your team owns everything.\u003cbr/\u003e\n\u003e ✅ 100% Open Source and backed by fanatical support.\u003cbr/\u003e\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e \u003cdetails\u003e\u003csummary\u003e📚 \u003cstrong\u003eLearn More\u003c/strong\u003e\u003c/summary\u003e\n\u003e\n\u003e \u003cbr/\u003e\n\u003e\n\u003e Cloud Posse is the leading [**DevOps Accelerator**](https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=commercial_support) for funded startups and enterprises.\n\u003e\n\u003e *Your team can operate like a pro today.*\n\u003e\n\u003e Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.\n\u003e #### Day-0:  Your Foundation for Success\n\u003e - **Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.\n\u003e - **Deployment Strategy.** Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.\n\u003e - **Site Reliability Engineering.** Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.\n\u003e - **Security Baseline.** Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.\n\u003e - **GitOps.** Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e\n\u003e #### Day-2: Your Operational Mastery\n\u003e - **Training.** Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.\n\u003e - **Support.** Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.\n\u003e - **Troubleshooting.** Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.\n\u003e - **Code Reviews.** Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.\n\u003e - **Bug Fixes.** Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.\n\u003e - **Migration Assistance.** Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.\n\u003e - **Customer Workshops.** Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.\n\u003e\n\u003e \u003ca href=\"https://cpco.io/commercial-support?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=commercial_support\"\u003e\u003cimg alt=\"Request Quote\" src=\"https://img.shields.io/badge/request%20quote-success.svg?style=for-the-badge\"/\u003e\u003c/a\u003e\n\u003e \n\u003c/details\u003e\n\n## ✨ Contributing\n\nThis project is under active development, and we encourage contributions from our community.\n\n\n\nMany thanks to our outstanding contributors:\n\n\u003ca href=\"https://github.com/cloudposse/terraform-aws-eks-cluster/graphs/contributors\"\u003e\n  \u003cimg src=\"https://contrib.rocks/image?repo=cloudposse/terraform-aws-eks-cluster\u0026max=24\" /\u003e\n\u003c/a\u003e\n\nFor 🐛 bug reports \u0026 feature requests, please use the [issue tracker](https://github.com/cloudposse/terraform-aws-eks-cluster/issues).\n\nIn general, PRs are welcome. We follow the typical \"fork-and-pull\" Git workflow.\n 1. Review our [Code of Conduct](https://github.com/cloudposse/terraform-aws-eks-cluster/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).\n 2. **Fork** the repo on GitHub\n 3. **Clone** the project to your own machine\n 4. **Commit** changes to your own branch\n 5. **Push** your work back up to your fork\n 6. Submit a **Pull Request** so that we can review your changes\n\n**NOTE:** Be sure to merge the latest changes from \"upstream\" before making a pull request!\n\n\n## Running Terraform Tests\n\nWe use [Atmos](https://atmos.tools) to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.\n\nAll tests are located in the [`test/`](test) folder.\n\nUnder the hood, tests are powered by Terratest together with our internal [Test Helpers](https://github.com/cloudposse/test-helpers) library, providing robust infrastructure validation.\n\nSetup dependencies:\n- Install Atmos ([installation guide](https://atmos.tools/install/))\n- Install Go [1.24+ or newer](https://go.dev/doc/install)\n- Install Terraform or OpenTofu\n\nTo run tests:\n\n- Run all tests:  \n  ```sh\n  atmos test run\n  ```\n- Clean up test artifacts:  \n  ```sh\n  atmos test clean\n  ```\n- Explore additional test options:  \n  ```sh\n  atmos test --help\n  ```\nThe configuration for test commands is centrally managed. To review what's being imported, see the [`atmos.yaml`](https://raw.githubusercontent.com/cloudposse/.github/refs/heads/main/.github/atmos/terraform-module.yaml) file.\n\nLearn more about our [automated testing in our documentation](https://docs.cloudposse.com/community/contribute/automated-testing/) or implementing [custom commands](https://atmos.tools/core-concepts/custom-commands/) with atmos.\n\n### 🌎 Slack Community\n\nJoin our [Open Source Community](https://cpco.io/slack?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=slack) on Slack. It's **FREE** for everyone! Our \"SweetOps\" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.\n\n### 📰 Newsletter\n\nSign up for [our newsletter](https://cpco.io/newsletter?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.\nDropped straight into your Inbox every week — and usually a 5-minute read.\n\n### 📆 Office Hours \u003ca href=\"https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=office_hours\"\u003e\u003cimg src=\"https://img.cloudposse.com/fit-in/200x200/https://cloudposse.com/wp-content/uploads/2019/08/Powered-by-Zoom.png\" align=\"right\" /\u003e\u003c/a\u003e\n\n[Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q\u0026A_ that you can’t find anywhere else.\nIt's **FREE** for everyone!\n## License\n\n\u003ca href=\"https://opensource.org/licenses/Apache-2.0\"\u003e\u003cimg src=\"https://img.shields.io/badge/License-Apache%202.0-blue.svg?style=for-the-badge\" alt=\"License\"\u003e\u003c/a\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003ePreamble to the Apache License, Version 2.0\u003c/summary\u003e\n\u003cbr/\u003e\n\u003cbr/\u003e\n\nComplete license is available in the [`LICENSE`](LICENSE) file.\n\n```text\nLicensed to the Apache Software Foundation (ASF) under one\nor more contributor license agreements.  See the NOTICE file\ndistributed with this work for additional information\nregarding copyright ownership.  The ASF licenses this file\nto you under the Apache License, Version 2.0 (the\n\"License\"); you may not use this file except in compliance\nwith the License.  You may obtain a copy of the License at\n\n  https://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing,\nsoftware distributed under the License is distributed on an\n\"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\nKIND, either express or implied.  See the License for the\nspecific language governing permissions and limitations\nunder the License.\n```\n\u003c/details\u003e\n\n## Trademarks\n\nAll other trademarks referenced herein are the property of their respective owners.\n\n\n---\nCopyright © 2017-2026 [Cloud Posse, LLC](https://cpco.io/copyright)\n\n\n\u003ca href=\"https://cloudposse.com/readme/footer/link?utm_source=github\u0026utm_medium=readme\u0026utm_campaign=cloudposse/terraform-aws-eks-cluster\u0026utm_content=readme_footer_link\"\u003e\u003cimg alt=\"README footer\" src=\"https://cloudposse.com/readme/footer/img\"/\u003e\u003c/a\u003e\n\n\u003cimg alt=\"Beacon\" width=\"0\" src=\"https://ga-beacon.cloudposse.com/UA-76589703-4/cloudposse/terraform-aws-eks-cluster?pixel\u0026cs=github\u0026cm=readme\u0026an=terraform-aws-eks-cluster\"/\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fterraform-aws-eks-cluster","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcloudposse%2Fterraform-aws-eks-cluster","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcloudposse%2Fterraform-aws-eks-cluster/lists"}