Chapter 1

1. CreateStack is invoked; CloudFormation then calls service APIs to create stack resources.
2. A CloudFormation service role is an IAM role that is assumed by CloudFormation before stack operations are performed. The policies attached to that role will then be used to perform stack operations.
3. The API credentials that are attached to the IAM entity (user or role), when we run the 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), the call will fail with a 400 AlreadyExists error.
6. If we run a stack update without any changes in a template or parameters, nothing will happen, as there are no changes. CloudFormation will not notice if the resource has been deleted manually. However, if we update the deleted resource, the operation will fail because the CloudFormation resource still exists in the state...