CloudFormation Core Operations and CDK Originated Stacks
Explore key CloudFormation operations to deploy and update AWS infrastructure safely using minimal change sets. Understand how CDK generates CloudFormation templates and how to interpret stack events for troubleshooting. Learn rollback mechanisms and best practices to ensure predictable infrastructure changes and maintain deployment confidence.
Infrastructure changes are easiest to trust when the smallest possible change is the one being tested first. A safe CloudFormation workflow starts with a tiny stack where one template change causes one predictable infrastructure change, so any surprise in the outcome has nowhere to hide behind. The example below creates an S3 bucket with server-side encryption and exports the bucket name as an output, giving a concrete proof point after each deploy. This stack is low-risk because it has no public ingress and no credentials, but it still incurs cost along normal axes, such as per-GB stored and per-request for S3.
The following template defines the minimal stack to provision an S3 bucket.
The topology implied by the template is simple, but operationally important. CloudFormation creates one AWS::S3::Bucket resource inside a single stack, and the stack becomes the boundary for change planning, execution, and rollback. The Outputs section is the contract surface that can be re-checked after any update to confirm what CloudFormation believes it created.
The illustration below shows a ...