A Terraform module to deploy Atlantis, a self-hosted Terraform collaboration tool, on AWS Fargate.
terraform-aws-atlantis is a Terraform module that deploys Atlantis, a self-hosted collaboration tool for Terraform, on AWS Fargate. It automates the provisioning of the complete AWS infrastructure required to run Atlantis, including ECS services, load balancers, and security configurations. This solves the problem of manually setting up and maintaining a secure, production-ready Atlantis deployment.
DevOps engineers, platform teams, and infrastructure developers who manage Terraform at scale and need a reliable, self-hosted collaboration workflow integrated with their AWS environment.
Developers choose this module because it provides a battle-tested, production-ready deployment of Atlantis with security best practices built-in. It significantly reduces setup time and maintenance overhead compared to manual deployments, while offering extensive customization options to fit existing AWS architectures.
Terraform module to deploy Atlantis on AWS Fargate 🇺🇦
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically provisions ECS, ALB, ACM certificates, and optional EFS with security groups and IAM roles, reducing manual setup as shown in the complete deployment example.
Supports creating all resources from scratch or integrating with existing ECS clusters and ALBs, demonstrated in the 'GitHub Separate' configuration for reuse.
Optional EFS integration ensures Terraform plan outputs survive task replacements, critical for reliable workflows, with configurable mount targets.
Uses AWS Secrets Manager for secrets, separates IAM roles, and includes default security group rules, aligning with best practices mentioned in the README.
With over 100 input variables and nested objects, setting up requires deep knowledge of both Atlantis and AWS services, making it error-prone for newcomers.
Heavily reliant on AWS-specific modules like ACM and ALB, with no built-in support for other clouds, limiting portability for hybrid strategies.
Provisions an ALB, ECS cluster, and optional EFS, which incur ongoing AWS charges even for light usage, unlike simpler serverless alternatives.