// the take
A large catalog of ~180 standalone Terraform root modules ('components') covering AWS services from VPCs and EKS add-ons to RDS, observability, and multi-account IAM, built to be deployed via Cloud Posse's Atmos orchestration tool rather than consumed as plain reusable Terraform modules. It's aimed at platform teams building out a full AWS landing zone who want Cloud Posse's opinionated reference architecture instead of assembling one from scratch.
Breadth is real: EKS alone has two dozen components for things like Karpenter, ALB controller, external-secrets, and cert-manager, each wired as its own deployable unit instead of one monolithic module. The Atmos stack/context pattern lets you parameterize the same component across dozens of account/environment combinations without copy-pasting Terraform. Years of production use across Cloud Posse's client base means the AWS edge cases (IAM trust policies, cross-account roles, SSO) are mostly already handled.
This specific repository is now archived and read-only — every component has been split out into its own repo under the cloudposse-terraform-components org, so anything you clone from here today is a frozen snapshot that will never get fixes or updates; you need to go find the new per-component repos instead. The components assume you're bought into Atmos and Cloud Posse's context.tf/stacks conventions, so pulling one component into a vanilla Terraform setup without the rest of the tooling is more friction than it looks like from the README. It's opinionated toward Cloud Posse's specific multi-account reference architecture, not a general-purpose module library, so partial adoption tends to drag in assumptions about account structure and naming you may not want.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →