Atlas vs AWS CloudFormation: What are the differences?
Atlas: Develop, deploy, and maintain your application anywhere. Use one console and one workflow from development to production. Atlas is one foundation to manage and provide visibility to your servers, containers, VMs, configuration management, service discovery, and additional operations services; AWS CloudFormation: Create and manage a collection of related AWS resources. You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order in which AWS services need to be provisioned or the subtleties of how to make those dependencies work.
Atlas and AWS CloudFormation can be categorized as "Infrastructure Build" tools.
What is Atlas?
What is AWS CloudFormation?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Atlas?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Atlas?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Atlas?
Sign up to get full access to all the tool integrationsMake informed product decisions
We use Terraform because we needed a way to automate the process of building and deploying feature branches. We wanted to hide the complexity such that when a dev creates a PR, it triggers a build and deployment without the dev having to worry about any of the 'plumbing' going on behind the scenes. Terraform allows us to automate the process of provisioning DNS records, Amazon S3 buckets, Amazon EC2 instances and AWS Elastic Load Balancing (ELB)'s. It also makes it easy to tear it all down when finished. We also like that it supports multiple clouds, which is why we chose to use it over AWS CloudFormation.
I use Terraform because it hits the level of abstraction pocket of being high-level and flexible, and is agnostic to cloud platforms. Creating complex infrastructure components for a solution with a UI console is tedious to repeat. Using low-level APIs are usually specific to cloud platforms, and you still have to build your own tooling for deploying, state management, and destroying infrastructure.
However, Terraform is usually slower to implement new services compared to cloud-specific APIs. It's worth the trade-off though, especially if you're multi-cloud. I heard someone say, "We want to preference a cloud, not lock in to one." Terraform builds on that claim.
Terraform Google Cloud Deployment Manager AWS CloudFormation
Manually clicking around the AWS UI or scripting AWS CLI calls can be both a slow and brittle process.
We needed to be able to reconstruct CloudRepo's infrastructure in case of disaster or moving to another AWS Region.
Setting up our infrastructure with CloudFormation allows us to update it easily as well as duplicate or recreate things when the need arises.
Opstax uses CloudFormation for anything infrastructure related! CloudFormation allows us to use infrastructure-as-code as a constant blueprint/map of our environment. It means we can accurately and efficiently deploy replicated or new infrastructure with no time wasted clicking around and no human error.
Manage infrastructure as codes. Native AWS solution so it has better support to AWS resources than Terraform, also can leverage AWS Business Support.