Chapter 1: CloudFormation Refresher

1. CreateStack.
2. CloudFormation Service Role is an IAM Role that is assumed by CloudFormation before stack operations are performed. The policies attached to that role will be then used to perform stack operations.
3. The ones that are attached to the IAM entity (User or Role), which run CloudFormation stack operations.
4. This information (physical resource ID and its metadata) is stored in CloudFormation's state.
5. If we try to create the same stack (that is, invoke the CreateStack API call), that call will fail with a 400 AlreadyExists error.
6. If we run a stack update without any changes in a template or parameters, nothing would happen as there are no changes. CloudFormation will not notice if the resource has been deleted manually. But if we update the deleted resource, the operation will fail, because the CloudFormation resource still exists in the state and CloudFormation believes it is still there.
7. Because CloudFormation...