How to set up Atlantis with GitHub webhooks?

Follow the official guide to configure a GitHub App or webhook, set environment variables for authentication, and deploy Atlantis on your server; it typically involves generating tokens and setting up a reverse proxy for security.

Atlantis vs Terraform Cloud: which is better for my team?

Choose Atlantis for self-hosted control and cost savings, ideal for teams comfortable with infrastructure management. Terraform Cloud offers a managed service with built-in state handling and enterprise support, better for those wanting less operational burden.

Does Atlantis support Terraform state locking?

Yes, Atlantis relies on Terraform's backend for state locking, so ensure your backend (like AWS S3 with DynamoDB) is properly configured; Atlantis itself doesn't add extra locking mechanisms.

Can Atlantis work with private Terraform modules?

Yes, but you need to configure credentials for module sources, such as GitHub tokens or cloud provider keys, in Atlantis's environment variables or project settings to allow access during plan/apply.

How to secure Atlantis deployments from unauthorized access?

Use HTTPS with TLS certificates, restrict network access, implement Git provider authentication (e.g., GitHub App), and manage secrets via environment variables or external tools like HashiCorp Vault.

What happens if a Terraform plan fails in Atlantis?

Atlantis comments the error output on the pull request, allowing developers to debug; you can configure retry logic or require manual intervention before proceeding, depending on your workflow settings.

Open-Awesome

atlantis

Apache-2.0Gov0.47.1

A self-hosted application that automates Terraform plan and apply workflows via pull request comments.

Visit Website GitHub

9.3k stars1.3k forks0 contributors

What is atlantis?

Atlantis is a self-hosted application that automates Terraform workflows through pull request integration. It listens for pull request events, runs Terraform plan and apply commands remotely, and posts the results as comments on pull requests. This brings infrastructure-as-code changes into the collaborative code review process.

Target Audience

DevOps engineers, platform teams, and infrastructure engineers who manage Terraform deployments and want to standardize and automate their infrastructure change workflows.

Value Proposition

Developers choose Atlantis because it integrates Terraform automation directly into the pull request workflow they already use, making infrastructure changes visible, collaborative, and consistent without requiring manual command-line execution.

Overview

Terraform Pull Request Automation

Use Cases

Best For

Automating Terraform plan and apply workflows from pull requests
Making infrastructure changes visible to entire engineering teams
Enabling non-operations engineers to safely collaborate on Terraform
Standardizing Terraform deployment processes across teams
Self-hosting Terraform automation for security and control
Implementing GitOps practices for infrastructure management

Not Ideal For

Teams already using managed Terraform services like Terraform Cloud or Spacelift
Organizations with multi-cloud IaC needs beyond Terraform, such as Pulumi or CloudFormation
Environments requiring vendor-supported SLAs and minimal operational overhead
Solo developers or small projects with simple Terraform workflows that don't need PR automation

Pros & Cons

Pros

Pull Request Automation

Automatically runs Terraform plan and apply on pull request events, commenting results directly on PRs for team visibility, as described in the README's core functionality.

Self-Hosted Control

Deploys on your own infrastructure for full security and data control, a key feature highlighted in the documentation for organizations wanting ownership.

Collaborative Visibility

Makes infrastructure changes accessible to non-operations engineers by integrating into existing PR workflows, enabling broader team participation in IaC management.

Workflow Standardization

Enforces consistent Terraform command execution across teams, reducing configuration drift and errors, as emphasized in the README's value proposition.

Cons

Self-Hosting Overhead

Requires ongoing server management, updates, and monitoring, adding operational complexity compared to SaaS alternatives that handle infrastructure for you.

Terraform-Only Limitation

Exclusively supports Terraform, lacking integration with other IaC tools like Pulumi or CloudFormation, which can be a drawback in mixed environments.

Setup Complexity

Initial configuration involves webhook setup, authentication, and permissions for Git providers, which can be non-trivial and time-consuming for new users.

Frequently Asked Questions

Related Projects

terraformer

CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code

Stars14,555

Forks1,839

Last commit6 months ago

$Infracost$ Infracost

Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!

Stars12,517

Forks688

Last commit5 days ago

Terragrunt

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/Terraform to scale.

Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.

Stars9,000

Forks1,406

Last commit3 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub