AWS CloudFormation vs Terraform: What are the differences?
Developers describe AWS CloudFormation as "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. On the other hand, Terraform is detailed as "Describe your complete infrastructure as code and build resources across providers". With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
AWS CloudFormation and Terraform belong to "Infrastructure Build Tools" category of the tech stack.
Some of the features offered by AWS CloudFormation are:
- AWS CloudFormation comes with the following ready-to-run sample templates: WordPress (blog),Tracks (project tracking), Gollum (wiki used by GitHub), Drupal (content management), Joomla (content management), Insoshi (social apps), Redmine (project mgmt)
- No Need to Reinvent the Wheel – A template can be used repeatedly to create identical copies of the same stack (or to use as a foundation to start a new stack)
- Transparent and Open – Templates are simple JSON formatted text files that can be placed under your normal source control mechanisms, stored in private or public locations such as Amazon S3 and exchanged via email.
On the other hand, Terraform provides the following key features:
- Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
- Execution Plans: Terraform has a "planning" step where it generates an execution plan. The execution plan shows what Terraform will do when you call apply. This lets you avoid any surprises when Terraform manipulates infrastructure.
- Resource Graph: Terraform builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, Terraform builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
"Automates infrastructure deployments" is the primary reason why developers consider AWS CloudFormation over the competitors, whereas "Infrastructure as code" was stated as the key factor in picking Terraform.
Terraform is an open source tool with 17.4K GitHub stars and 4.77K GitHub forks. Here's a link to Terraform's open source repository on GitHub.
Instacart, Slack, and Twitch are some of the popular companies that use Terraform, whereas AWS CloudFormation is used by TimeHop, Custora, and NASA Jet Propulsion Laboratory. Terraform has a broader approval, being mentioned in 490 company stacks & 298 developers stacks; compared to AWS CloudFormation, which is listed in 195 company stacks and 75 developer stacks.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is AWS CloudFormation?
What is Terraform?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions