CloudFormation stack deployment failed, how to check and fix it?

[Paul-AWS]

When deploying CloudFormation stack of Centralized Logging with OpenSearch, i received a red error shows that the stack create failed. How to get the root cause and fix it?

[Paul-AWS]

When CloudFormation Stack is not successfully deployed, it is generally due to limitations when creating certain resources. You can check the reasons and resolve them by following the steps below.

Step 1. Log in to your AWS account, search for the CloudFormation service, and go to the CloudFormation console. In the list of stacks on the left, find the stack that you deployed and select the "Events" tab on the right.

Step 2. You'll see some error messages in the color of red, please keep scrolling down until you find the earliest error message, which is the root cause of the unsuccessful deployment. Based on the error message you see, make the appropriate adjustments.

Here are some common error messages and solutions:

• Insufficient VPCs: If you select “Deploy from a new VPC”, Centralized Logging with OpenSearch will create a new VPC for you. However, if the number of VPCs in your account has reached the limit, the creation of a VPC will fail, and the stack deployment will fail. You can fix this by creating a Support Case to increase the VPC limit or delete the existing unused VPCs.
• Insufficient Elastic IPs: Centralized Logging with OpenSearch will create two EIPs for you. However, if the number of EIPs in your account has reached the limit, the creation of them will fail, which case the stack deployment failure. You can fix this by creating a Support Case to increase the EIP limit or delete the existing unused VPCs.
• Unable to create S3 bucket: Centralized Logging with OpenSearch will create four S3 buckets to store the static resources for console and logs. If the number of S3 buckets in your account has reached the maximum limit, the creation of the S3 buckets will fail, which case the stack deployment failure. You can fix this by creating a Support Case to increase the number of S3 bucket limits or delete the S3 buckets you don't need.
• AppSync assume role failed (Error: Failed to assume service-linked role arn:xxx:/AWSServiceRoleForAppSync): Centralized Logging with OpenSearch use AppSync to build the console. The reason for this error is that the account has never used the AWS AppSync service. You can deploy the solution's CloudFormation template again to. AWS has already created the role automatically when you encountered the error. You can also go to AWS CloudShell or the local terminal and run the following AWS CLI command to Link AppSync Role.
  aws iam create-service-linked-role --aws-service-name appsync.amazonaws.com