TerraformPilot

Infrastructure as Code

terraform-aws-eks v21.30.2: Bug Fix for Cluster Reference Guards and ami_type Null Check

terraform-aws-eks module v21.30.2 patches a bug guarding cluster references with local.create and simplifies ami_type null checks.

LLuca Berton2 min read

Introduction

#

The terraform-aws-modules/terraform-aws-eks module — the most widely used community module for provisioning Amazon EKS clusters with Terraform — released v21.30.2 on 2026-11-17. This is a small patch release on top of v21.29.0/v21.30.1, and the release notes are thin: a single bug fix. This article covers exactly what changed and how to upgrade safely.

What Is New

#

The release notes for v21.30.2 list one change:

  • Bug Fix: Guard cluster references with local.create and simplify the ami_type null check (#3758, commit 95d648c).

In practice, this fix addresses references to cluster attributes that were not properly guarded by the module's internal local.create flag — the flag the module uses internally to decide whether a resource/data source block should actually be created (relevant when you set create = false on the module or on sub-resources). Without the guard, certain cluster-related references could be evaluated even when the cluster resource itself wasn't being created, which can surface as plan-time errors or inconsistent plans in conditional/count-based module usage. The ami_type null check was also simplified as part of the same fix, reducing the chance of unexpected null comparisons when ami_type is left unset on managed node groups.

No new input variables, no new outputs, and no deprecations are mentioned in this release. If your configuration doesn't use create = false (or conditional creation patterns) on the module or doesn't rely on a bare ami_type, this patch is unlikely to change observable behavior for you — it is primarily a correctness/robustness fix.

Because the published notes don't go into further detail, check the full diff and commit for context if you need more than what's summarized here: https://github.com/terraform-aws-modules/terraform-aws-eks/releases/tag/v21.30.2

Upgrade Steps

#

Pin the module version explicitly and bump it:

module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "21.30.2"
 
  # ... your existing cluster configuration
}

If you use a version constraint range instead of an exact pin:

module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 21.30"
 
  # ... your existing cluster configuration
}

Re-initialize to pull the new module version:

terraform init -upgrade

Then run a plan to confirm no unexpected changes before applying:

terraform plan

Since this is a bug fix touching internal conditional logic, pay particular attention to the plan output if your configuration uses create = false anywhere in the module call, or omits ami_type on managed node groups — these are the code paths the patch touches.

Verify

#

Confirm the module version actually in use:

terraform providers
terraform state list | grep module.eks

Or check the lock/init output directly:

terraform init -upgrade
# Look for: Installing terraform-aws-modules/eks/aws v21.30.2

Run terraform plan and confirm it reports no changes (or only expected changes) — this patch should not alter any resource configuration for typical cluster setups.

Conclusion

#

v21.30.2 of terraform-aws-eks is a targeted bug fix release addressing a local.create guarding issue and an ami_type null-check simplification. There are no breaking changes, new features, or deprecations in this release. Teams running conditional module creation (create = false) or omitting ami_type should upgrade to pick up the more robust guards; everyone else can treat this as a routine patch bump.

#Terraform#AWS EKS#Terraform AWS Modules#Kubernetes#AWS

Share this article