FAQ

Q: Does Atlantis affect Terraform remote state?

A: No. Atlantis does not interfere with Terraform remote state in any way. Under the hood, Atlantis is simply executing terraform plan and terraform apply.

Q: How does Atlantis locking interact with Terraform locking?

A: Atlantis provides locking of pull requests that prevents concurrent modification of the same infrastructure (Terraform project) whereas Terraform locking only prevents two concurrent terraform apply's from happening.

Terraform locking can be used alongside Atlantis locking since Atlantis is simply executing terraform commands.

Q: How to run Atlantis in high availability mode? Does it need to be?

A: Atlantis server can easily be run under the supervision of a init system like upstart or systemd to make sure atlantis server is always running.

Atlantis, by default, stores all locking and Terraform plans locally on disk under the --data-dir directory (defaults to ~/.atlantis). If multiple Atlantis hosts are run by utilizing a shared redis backend, then it's important that the data-dir is using a shared filesystem between hosts.

However, if you were to lose the data, all you would need to do is run atlantis plan again on the pull requests that are open. If someone tries to run atlantis apply after the data has been lost then they will get an error back, so they will have to re-plan anyway.

Q: How to add SSL to Atlantis server?

A: First, you'll need to get a public/private key pair to serve over SSL. These need to be in a directory accessible by Atlantis. Then start atlantis server with the --ssl-cert-file and --ssl-key-file flags. See atlantis server --help for more information.

Q: How can I get Atlantis up and running on AWS?

A: There is terraform-aws-atlantis project where complete Terraform configurations for running Atlantis on AWS Fargate are hosted. Tested and maintained.