Terraform vs CloudFormation

Overview

Terraform and AWS CloudFormation both define infrastructure as code, but with different scopes. Terraform is cloud-agnostic and manages resources across AWS, Azure, GCP, and hundreds of other providers. CloudFormation is AWS's native service, deeply integrated but AWS-only. The choice often comes down to portability versus native AWS depth.

Key Differences

Terraform's defining strength is multi-cloud reach. One tool and one language (HCL) provision resources across many clouds and SaaS platforms. Its module and provider registry is the largest in IaC, and HCL is generally more concise and readable than CloudFormation's JSON or YAML templates. You manage state yourself or through HCP Terraform.

CloudFormation's strength is being part of AWS. AWS manages state for you as stacks, removing a class of operational concerns. New AWS services and features often gain CloudFormation support on or near launch day, whereas Terraform's AWS provider can lag slightly. CloudFormation also offers automatic rollback when a stack update fails, returning resources to the last known-good state, and integrates with StackSets for multi-account deployment.

Template authoring differs. Raw CloudFormation in JSON/YAML is verbose, but the AWS CDK lets you write CloudFormation in TypeScript, Python, and other languages, narrowing Terraform's developer-experience advantage. Drift detection exists in both, though Terraform surfaces it as part of its plan workflow.

When to Choose Terraform

Choose Terraform when you operate across multiple clouds or use non-AWS providers, or when you want a single, portable IaC tool with a vast ecosystem. Its concise HCL and community modules speed up authoring, and it avoids lock-in to any one provider's tooling.

When to Choose CloudFormation

Choose CloudFormation when you are committed to AWS and want native integration. Managed state, automatic rollback, same-day feature support, and tight links to AWS governance tools like StackSets and Service Catalog are real advantages for AWS-only estates. The CDK makes authoring pleasant for developers.

Verdict

If you are multi-cloud or value ecosystem and portability, Terraform is the clear pick. If you are firmly AWS-only and want managed state, automatic rollbacks, and the earliest feature support, CloudFormation (often via the CDK) is excellent. Some AWS teams use both: CloudFormation for AWS-native pieces and Terraform where multi-cloud or third-party providers are involved.