CloudFormation has several actions associated with it, which are defined up front so that they can be used to make rest of the videos efficiently
- [Instructor] Let's cover four of the most commonly used verbs related to CloudFormation. The first one is create. It refers to the creation of a CloudFormation stack from a CloudFormation template. During create, all resources specified in a template are created. Users often want to update an existing stack, which triggers an update operation. When an update is triggered, CloudFormation computes a chain set, which is the action required to make the current stack match the requested state.
It can then applies those changes to complete an update. Just like create and update, users also delete stacks, which deletes all related resources. This may seem dangerous as a user may accidentally delete a stack and take down production. But, there are multiple levels of protection against this. First, we enable termination protection on the stacks to prevent accidental deletion. Next, we specify deletion policies for stateful resources such as databases and S3 buckets that we do not want deleted even if the stack delete is triggered.
If a delete, create, or an update operation fails, CloudFormation attempts a rollback. Rollback is an operation the CloudFormation triggers itself in attempts to roll back all changes made by the operation to restore the stack to its state prior to the operation. With these four actions, we can control the entire life cycle of a CloudFormation stack.
- Infrastructure as code
- CloudFormation architecture
- Deploying S3 buckets and EC2 web servers
- Advanced topics