OSS TanbouOn this page
Overview
terraform-aws-eks packages Amazon EKS control planes, managed node groups, access settings, and related AWS resources behind Terraform inputs. Teams can review environment differences as code and standardize cluster configuration through plans and review.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Best fit
Before adoption
Official sources
- [1]terraform-aws-modules/terraform-aws-eks README at v21.26.0(2026-10-05)
- [2]Terraform AWS EKS official documentation(2026-10-05)
- [3]Terraform AWS EKS fixed version source(2026-10-05)
- [4]terraform-aws-modules/terraform-aws-eks LICENSE at v21.26.0(2026-10-05)
- [5]terraform-aws-modules/terraform-aws-eks GitHub metadata(2026-10-05)
Supplemental curator note
It suits teams moving EKS configuration from per-environment manual work into reviewable code. First initialize and validate the pinned module with placeholder IDs, then separately review real networking, permissions, and cost before any apply.
Try it in 3 steps
- 1
Write a pinned EKS configuration
Requires Terraform 1.5.7 or later. Pin 21.26.0 in a temporary directory with placeholder VPC and subnet IDs used only for validation.
demo=$(mktemp -d "${TMPDIR:-/tmp}/eks-module.XXXXXX") && cd "$demo" && printf '%s\n' 'terraform { required_version = ">= 1.5.7" }' 'module "eks" {' ' source = "terraform-aws-modules/eks/aws"' ' version = "21.26.0"' ' name = "validation-only"' ' kubernetes_version = "1.34"' ' vpc_id = "vpc-00000000000000000"' ' subnet_ids = ["subnet-00000000000000000"]' '}' > main.tf - 2
Initialize without a backend
Download the pinned module and required providers locally without configuring a state backend. No AWS credentials are used.
terraform init -backend=false -input=false - 3
Validate without contacting AWS
Run terraform validate for syntax and module-input checks. Do not run plan or apply, and create no AWS resources.
terraform validate
Growth
Growth trends · Last 30 days
5,008 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 10
- Open PRs
- 6
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- terraform
- terraform-module
- aws
- kubernetes
- eks
- elastic-kubernetes-service
- aws-eks
- aws-eks-cluster
- Stars
- 5,008
- Forks
- 4,413
- Watchers
- 95
- Open issues
- 5
- Contributors
- 382
- Owner type
- Organization
- Primary language
- HCL
- License
- Apache-2.0
- Repository last updated
- Sep 28, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- Kustomize12,177 Stars
1 shared tag(s) · 1 shared category(s)
Declaratively layer environment-specific changes while keeping original Kubernetes YAML intact
Go - Crossplane12,133 Stars
1 shared tag(s) · 1 shared category(s)
extend Kubernetes APIs to build cloud-native control planes for applications and infrastructure
Go - Flux8,436 Stars
1 shared tag(s) · 1 shared category(s)
continuously reconcile Kubernetes with desired state declared in Git or OCI and automate delivery through GitOps
Go - Argo Rollouts3,592 Stars
1 shared tag(s) · 1 shared category(s)
control blue-green and canary delivery with Kubernetes CRDs, traffic shaping, metrics, promotion, and rollback
Go - Kong Gateway44,240 Stars
1 shared tag(s)
Centralize API routing, authentication, and traffic control at a shared gateway
Lua - Encore12,411 Stars
2 shared tag(s) · 1 shared category(s)
Derive infrastructure requirements from application code from local development to cloud deployment
Go
Report incorrect information
Tell us if any listing information is incorrect or outdated.