AWS Certified CloudOps Engineer - Associate
CloudFormation Stack Operations
Changing a running stack without breaking it: the three update behaviors, change sets, stack policies, signals and rolling updates, rollback options and triggers, drift detection, nested stacks, and importing existing resources.
Intermediate 30 minutes 7 Learning Objectives
- Classify an update as no interruption, some interruption, or replacement, and predict the effect on the physical ID
- Use a change set to preview an update, and state what a change set cannot promise
- Write a stack policy that protects a critical resource, and explain why it is not a substitute for IAM
- Configure CreationPolicy and UpdatePolicy so a stack waits for the application rather than the API
- Choose between automatic rollback, preserved resources, and rollback triggers for a given deployment
- Interpret drift detection results and name the cases where drift cannot be detected
- Compare nested stacks with separate stacks joined by cross-stack references