AWS CloudFormation

AWS CloudFormation provisions and manages AWS resources from declarative templates, treating a group of resources as a single stack that can be created, updated and deleted together. It is a managed service within AWS rather than a tool an organisation runs, and it understands the resources it manages because it is part of the platform providing them.

Being native is the advantage and the constraint in the same sentence. Support for a new AWS capability arrives with the capability itself, and the service manages nothing outside AWS, so an organisation running workloads in more than one cloud needs something else alongside it.

The stack as a unit is the concept to grasp. Creating and deleting a whole environment as one object makes teardown reliable, which matters more than creation: leftover resources from partially removed environments are one of the most common sources of unexplained cloud spend.

Rollback on failure is the operational behaviour worth understanding before relying on it. A failed update returns the stack to its previous state automatically, which is exactly what is wanted most of the time and occasionally the opposite, so knowing how to handle a stack stuck mid-rollback is part of operating it.