// the find
aws-ia/terraform-aws-eks-blueprints
Configure and deploy complete EKS clusters.
A reference library of Terraform patterns for standing up opinionated EKS clusters with common add-ons pre-wired (Karpenter, ArgoCD, Istio, Fargate, etc.). This is copy-paste starter material maintained by AWS Solution Architects, not a Terraform module you pin as a dependency. Aimed at teams that want a validated starting point rather than building from scratch.
1. Breadth of patterns is genuinely useful: blue/green cluster upgrades, multi-cluster ArgoCD hub-spoke, Bottlerocket nodes, GPU/EFA for ML workloads, and IPv6 are all covered with working Terraform. 2. The gitops-bridge pattern for passing cluster metadata to ArgoCD is a clean solve for the chicken-and-egg problem of bootstrapping add-ons. 3. Actively maintained (pushed June 2026) with e2e CI that actually plans and applies examples — not just lint. 4. The separation into singular `addon` vs plural `addons` modules lets you compose at the right granularity without being forced into the full opinionated stack.
1. Not a module — the README says so explicitly, but that means you're copying HCL into your repo and owning the drift forever. There's no upgrade path; you just re-copy or manually reconcile. 2. Everything-in-one-workspace approach violates Terraform's own guidance (computed values in provider blocks), and the workaround — targeted apply — is fragile and undocumented for new users who won't read the FAQ. 3. Patterns bundle a VPC because it makes CI easier, which means you'll rip out the VPC block on day one and debug provider initialization issues that weren't obvious from the example. 4. No test infrastructure beyond CI plan/apply — there are no unit or integration tests you can run locally before spending $20 spinning up a real cluster to validate a change.