terraform-aws-eks VS terraform-aws-security-group

Ref: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/v20.36.0/examples/eks-auto-mode/main.tf

Cluster creation is straightforward. We’ll use the state file from the VPC creation to retrieve outputs, and we’ll create the cluster using the terraform-aws-modules/eks/aws module.

If you are using https://github.com/terraform-aws-modules/terraform-aws-eks module to create your cluster and using in-built role it is creating for the worker nodes, don’t forget to extend it with a new policy to allow ecr:BatchImportUpstreamImage because by default it attaches managed policy arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryPullOnly which doesn’t allow pull-through cache.

From the documentation, we have to use CUSTOM value, but it is not true. There is a github issue: #3094. Terraform is not accepting the CUSTOM value. Instead of CUSTOM it has to be value, which the image is based on. In my example, it is AL2023_x86_64_STANDARD.

I have used eks auto using terraform eks module which is quick and easy.

Terraform-aws-eks release a new version v20.31.1 which allows to use custom NodeClass/NodePools when EKS Auto is enabled without built-in NodePools.

Terraform eks module released a new version v20.31.0 which enables the support of EKS Auto mode and EKS Hybrid Nodes.

Note: Terraform support(still ongoing) not yet there so for this blog we will use AWS console.

Here’s a lovely GitHub issue with more details: https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1539

Upon reviewing EKS Blueprints, I found myself pondering its relationship with terraform-aws-modules-eks. In reality, EKS Blueprints does not stand in opposition to or compete with terraform-aws-modules-eks; rather, it complements and extends its functionality. EKS Blueprints acts as a valuable enhancement to the standard EKS module, enriching it with additional features and refinements, effectively adding a touch of sweetness and spice to the existing framework.