AWS CloudFormation

AWS CloudFormation models, provisions, and manages related AWS and third-party resources as infrastructure as code. Users describe AWS resources and their properties in YAML or JSON templates and manage them as stacks. Change Sets preview proposed updates, including potential resource deletion or replacement, before execution; Drift Detection identifies changes made outside the service. StackSets provision a shared resource set across multiple AWS accounts and Regions. Authoring options include AWS CDK, which supports TypeScript, Python, Java, and .NET, and AWS SAM, which provides shorthand YAML for serverless functions, APIs, databases, and event mappings that is converted to CloudFormation syntax during deployment. The Registry supports third-party resources and modules, and stacks can be updated from remote Git repositories. IAM can control access, and CloudTrail logs API calls. CloudFormation data is encrypted at rest and service communications use encrypted channels; AWS recommends TLS 1.3 and requires TLS 1.2. CloudFormation itself has a free plan, but AWS resources created through it are billed at their standard rates. Third-party provider and custom hook operations may also incur charges.

CloudFormation provides template-based management for AWS and supported third-party resources, with previews and drift tracking for stack changes. Its free plan covers CloudFormation itself, not the AWS resources created through it.

CloudFormation may suit teams managing AWS infrastructure through templates, including CI/CD workflows and deployments spanning accounts or Regions. It also supports users authoring environments with CDK or serverless resources with SAM.

AWS CloudFormation is a managed infrastructure-as-code service for defining AWS environments. It is strongest for teams standardizing deployments within AWS, especially when infrastructure must span accounts or Regions. Its AWS focus is also its clearest boundary for organizations seeking a common workflow across cloud providers.

Overview

CloudFormation groups related resources into stacks described by templates, supporting workflows from a single EC2 instance to complex multi-Region applications and CI/CD-driven infrastructure updates. Managed state, resource import, policy as code, and self-hosted execution give teams several ways to fit it into existing operations. The trade-off is that its supported cloud is AWS, so it is not a natural control plane for a mixed-cloud estate.

CloudFormation itself is free for AWS and Alexa resource providers, but the resources it creates are billed at their standard AWS rates. Third-party provider and custom hook operations may also incur charges, so a free service plan should not be mistaken for free infrastructure.

Key features

Templates and authoring choices

YAML and JSON templates declare AWS resources and their properties. Teams can instead define cloud environments in TypeScript, Python, Java, or .NET with the AWS CDK, which provisions through CloudFormation. AWS SAM adds shorthand YAML for serverless functions, APIs, databases, and event source mappings, transforming it into CloudFormation syntax during deployment. These options accommodate different authoring styles while keeping deployments on the same AWS service.

Change control and drift

Change Sets preview proposed stack updates and flag when resources may be deleted or replaced. That makes potentially disruptive changes easier to identify before execution, though teams still need to assess the effect of a proposed change. Drift Detection tracks resource changes made outside CloudFormation, helping operators find when actual infrastructure no longer matches the managed stack.

Scale and extensibility

StackSets deploy a shared set of AWS resources across multiple accounts and Regions from one template, a practical fit for organizations standardizing infrastructure across environments. The CloudFormation Registry also supports third-party resources and modules, including examples such as MongoDB, Datadog, Atlassian Opsgenie, JFrog, and Splunk. Remote Git repository templates support a development workflow tied to version-controlled infrastructure.

Security and oversight

CloudFormation data is encrypted at rest and service communications use encrypted channels; AWS recommends TLS 1.3 and requires TLS 1.2. IAM can control access, while CloudTrail logs API calls. These controls support access management and auditing, but teams remain responsible for configuring them appropriately.

Pricing

AWS CloudFormation: free. The service is free for CloudFormation itself, while underlying AWS resources are billed at their own rates. Third-party provider and custom hook operations may incur charges: the first 1,000 operations are included in the Free Tier, and the first 30 seconds of each operation have no additional charge.

There is no free trial because the service has a free plan. This is a straightforward fit for AWS users who want stack management without a separate CloudFormation service charge, but it does not cap the costs of deployed AWS resources or necessarily eliminate charges for third-party operations.

Platforms

CloudFormation supports API, Linux, macOS, web, and Windows. YAML and JSON are its configuration languages, and AWS is its supported cloud.

Who it's for

CloudFormation suits AWS teams that need repeatable infrastructure deployments, centralized stack management, or consistent provisioning across accounts and Regions. CI/CD teams can use templates to automate infrastructure, while operators benefit from previews and drift tracking. Teams whose primary need is one infrastructure workflow across multiple clouds should consider a different fit.

Pros and cons

• Pros: Change Sets surface possible deletion or replacement before execution, giving teams a useful review point for stack updates.
• Pros: StackSets extend a single template across accounts and Regions, reducing friction in standardized AWS deployments.
• Pros: CDK, SAM, and Registry support offer multiple authoring approaches and third-party resource options.
• Cons: AWS is the only supported cloud, limiting its fit for organizations that need a unified multi-cloud workflow.
• Cons: Free CloudFormation service usage does not cover AWS resources created through it, and some third-party operations can cost extra.

Alternatives

Terraform is worth considering for teams seeking an infrastructure-as-code option with a free plan, free trial, and support for API, Linux, macOS, self-hosted, web, and Windows environments. Its Free plan includes 500 managed resources, one concurrent remote run, and one concurrent agent run.

Cloudify may suit teams looking for a free Community plan with no time limit, provided they are prepared to set it up on Docker or a VM and have access to a cloud provider for workloads.

env0 is an option for teams that want a free tier with up to 250 monthly runs, 30 active environments, one concurrent run, and unlimited users and agents.

OpenTofu is a free, open-source infrastructure-as-code alternative for teams who prefer that model.

Pulumi offers a free plan with one user, unlimited projects, stacks, environments, updates, and history, making it an alternative for an individual working across multiple projects.

Scalr may fit teams that want up to 50 runs per month free, with business usage priced at $0.99 per run and volume discounts.

Spacelift is another freemium option; its Free plan includes two users and one public worker.

Terragrunt is an alternative with a free plan covering up to 25 infrastructure units.

Compare more options in Infrastructure as Code Tools, Cloud Orchestration Software, Infrastructure Testing Tools, IT Configuration Management Software, Infrastructure Policy as Code Tools, and Infrastructure as Code Security Software.

Verdict

Choose AWS CloudFormation if your infrastructure is centered on AWS and you value stack-based deployments, cross-account and cross-Region provisioning, and previews before changes execute. Its service charge is zero, but resource bills remain, and its AWS-only scope is the main reason to look elsewhere.