AWS CloudFormation vs Terraform Comparison: Everything You Need to Know Before Choosing

AWS CloudFormation is an infrastructure-as-code service from Amazon Web Services that allows organisations to model, provision and manage their cloud resources using templates. It addresses the complexity and risk involved in setting up and maintaining cloud environments manually, where configuring networks, compute instances, databases, security settings and other resources through consoles or ad hoc scripts is time-consuming, error-prone and difficult to reproduce consistently. CloudFormation’s approach is to describe infrastructure declaratively in JSON or YAML templates, which the service then uses to create and update resources in a controlled, repeatable way. Groups of resources are managed together as stacks, with CloudFormation handling dependencies and the order of operations. This enables teams to version-control their infrastructure alongside application code, apply changes predictably and replicate environments across accounts and regions, supporting DevOps practices and governance at scale. Key capabilities include stack creation, update and deletion, change sets that preview the effects of proposed modifications, drift detection to identify resources changed outside CloudFormation, and rollback on failure. StackSets enable deployment across multiple AWS accounts and regions, while nested stacks and modules support reusable components. The CloudFormation Registry allows the use of third-party and custom resource types, and hooks support policy checks before provisioning. Developers can author templates directly or use higher-level tools such as the AWS Cloud Development Kit and AWS Serverless Application Model, which generate CloudFormation templates. The service integrates with AWS Identity and Access Management, CodePipeline and other AWS services to support secure, automated deployment pipelines. As a managed service within AWS, it requires no separate infrastructure. It is used by developers, DevOps engineers, platform teams and cloud architects in organisations of all sizes running workloads on AWS. Pricing is not published in this listing; in practice, AWS charges for the resources provisioned and for certain third-party resource operations rather than for standard use of the service itself.