#4 of 28 infrastructure automation tools · Updated October 2026
CloudFormation review 2026
AWS CloudFormation (with the AWS CDK) · Dependable builder
CloudFormation ranks #4 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 62 out of 100. AWS CloudFormation with the CDK: strong planning, safety and AWS depth, no target outside AWS, and a managed MCP server since May 2026.
Scores
Source: Infrastructure Automation Ledger 2026, edition 2026-10-16. How each score works: methodology.
Pros
- State, planning and safety4.5/5
- Language and authoring4/5
- Scale and control plane4/5
- Security and compliance4/5
Cons
- Configuration management depth1/5
- Bare metal and day-2 operations1/5
- Provisioning breadth2.5/5
What the Ledger says
CloudFormation sits in this Ledger as the single-cloud reference, and its scores read that way: planning, safety and security are near the top of the field inside AWS, while provisioning breadth and bare metal stay low because nothing outside AWS can be described in a template. Credibility is steady: features arrive at GA without pre-announcement and the engine has kept its shape since 2011, though the authoring tools around it churn (Infrastructure Composer, the Q Developer plugins, CDK for Terraform). Lock-in is the highest in the group by design, since state, formats and the control plane all live in one cloud and the only import path points inward. A buyer planning on the CDK should check the status of cdk refactor, still a preview 13 months after launch, before committing to large restructures.
AWS has two agent routes around CloudFormation: a managed AWS MCP Server with IAM guardrails and CloudTrail logging, GA since 2026-05-06 in two Regions, and a local open-source IaC MCP server that searches documentation, lints templates and checks Guard rules but cannot create a stack. Code generation sits in Amazon Q Developer, whose IDE plugins reach end of support on 2027-04-30 with Kiro named as the successor and no published statement on CloudFormation generation. There is no plan explanation feature and no AI in CloudFormation's own operations.
Capability by area
Buying, lock-in and release record
Buying and licence (commercial risk)(lower is better)
- Price and licence volatility0.5
- No charge for AWS-namespace resources in every source read; per-operation fee for third-party types and hooks; no price change found
- Purchase constraints1
- Nothing to buy, but an AWS account is required and there is no standalone product
- Channel and access0.5
- Open to any AWS customer; CDK and the CloudFormation CLI are open source on GitHub and npm
- Owner stability0.5
- Built in house by Amazon Web Services; no ownership change
- Cost of staying supported1.5
- No upgrade fees; surrounding tools retired on notice (Infrastructure Composer console 2026-12-07, Q Developer IDE plugins 2027-04-30)
Technical lock-in(lower is better)
- Formats3.5
- AWS-specific template schema and CDK constructs; state lives inside the service
- Export path3
- IaC generator imports into templates; no exporter to another tool; CDK for Terraform archived 2025-12-10
- Stack coupling4
- AWS resources only; registry extensions run and bill inside AWS
- Hardware / cloud coupling4.5
- Managed service only; no self-hosted or air-gapped mode; pre-deployment validation excludes China Regions
- Skills and tooling coupling2
- Large AWS skills pool; CDK in five general-purpose languages; Guard and cfn-lint are AWS specific
Release credibility
- Cadence4
- CDK library every one to two weeks (ten releases from 2026-08-10 to 2026-10-08); service changes monthly; no published rhythm
- Roadmap transparency3
- Dated What's New posts and blogs; no dated service roadmap read
- Say-do3.5
- Most features reach GA at announcement; cdk refactor in preview for 13 months; Git sync GA date not found
- Velocity4
- Several substantive items per quarter in 2025-11 and 2026-06
- Lifecycle stability3
- Engine stable since 2011; authoring tools renamed and retired (Infrastructure Composer, Q Developer IDE plugins, CDK for Terraform)
Partners and services
- Partner programme openness3.5
- AWS Partner Network exists; its terms were not read for this edition
- Multi-tenancy and self-service4
- StackSets with AWS Organizations, Service Catalog and Control Tower managed hooks; the account is the tenant, there is no customer portal
- API and infrastructure-as-code5
- Every action is an API; Cloud Control API gives uniform create, read, update, delete and list; CDK Toolkit Library embeds the deploy engine
- Skills and certification4
- AWS certifications and a very large skills pool; specific tracks not checked
Alternatives to CloudFormation
Questions about CloudFormation
Is CloudFormation any good?
CloudFormation ranks #4 of 28 infrastructure automation tools in the Infrastructure Automation Ledger 2026, with a Ledger Index of 62 out of 100. Its strongest areas are state, planning and safety, language and authoring, scale and control plane. Its weakest are configuration management depth, bare metal and day-2 operations, provisioning breadth.
What are the best alternatives to CloudFormation?
The closest by Ledger Index are Pulumi (61.2), Ansible (60.4), Bicep (59.6), Harness IaCM (59.3).
How is CloudFormation licensed and sold?
No charge for AWS-namespace resources in every source read; per-operation fee for third-party types and hooks; no price change found.
How much lock-in does CloudFormation bring?
CloudFormation scores 17 out of 25 on technical lock-in (lower is better). Export path: IaC generator imports into templates; no exporter to another tool; CDK for Terraform archived 2025-12-10.
User reviews of CloudFormation
No reviews yet
Be the first to say how CloudFormation worked for you.
Write a review
No account needed and no email asked. We read every review before it appears and remove adverts, spam and personal attacks.