// the find
turnerlabs/terraform-ecs-fargate
A Terraform template used for provisioning web application stacks on AWS ECS Fargate
A Terraform template (not a module) for standing up a web application on AWS ECS Fargate with an ALB, autoscaling, secrets management, and a CI/CD IAM user. It's a copy-and-modify starting point, not something you import. The maintainers themselves recommend migrating to the newer Warner Media module version.
- Flat-file, à-la-carte design means you delete optional .tf files rather than fighting feature flags — genuinely easier to reason about for teams new to Terraform
- Covers the real operational surface area most teams need: ALB listeners (HTTP and HTTPS separately), performance and time-based autoscaling, Secrets Manager with CMK, SSM Parameter Store, and a CloudWatch dashboard all as optional drop-ins
- The cicd.tf IAM user with scoped permissions is a practical, copy-pasteable pattern that saves people from creating overly-permissive CI credentials
- Still being maintained for provider/Terraform compatibility despite being superseded, so it won't suddenly break on a fresh clone
- Only one environment directory (env/dev) exists in the repo; multi-environment setups require manually duplicating that directory with no guidance on how to DRY it across envs, which leads to copy-paste drift
- The README explicitly says to abandon this in favor of the module version, which means any time you spend customizing this is investment in a dead end — new features won't land here
- Base state is stored locally and must be checked into version control, which is a footgun the README buries in a small callout after the apply step
- No example of VPC creation — it assumes an existing VPC and subnets, so you either wire it to pre-existing infra or end up stitching in a separate VPC module with no guidance on how the two connect