Problem
When creating a CloudFormation stack, it may fail due to various reasons.
Solution
Possible reasons and their solutions:
The IAM role you have selected during the CloudFormation stack creation may not have sufficient permissions.
If you have not select an IAM role, make sure your account not have the required permissions.
If the failure message appears as following, delete or rename the existing resources with that name, and retry.
Resource type {resource-name} with identifier {resource-identifier-name} already exists.Check the output of the nested CloudFormation stacks to identify potential errors.
Ensure the selected S3 buckets don’t have event notifications on any object creation events.
Ensure the selected CloudWatch log groups don’t have similar subscription filters.