CID dashboard stack creation failure

The error you're encountering during the CID (Cloud Intelligence Dashboards) stack creation is likely due to an S3 bucket naming conflict. S3 bucket names must be globally unique across all AWS accounts. When the CloudFormation stack tries to create a bucket that already exists (either in your account or someone else's), it will fail.

To resolve this issue:

1. Try using a different, unique bucket name in your CloudFormation template. You can modify the BucketName property in your template to something that's less likely to be taken.

2. If you're intending to use an existing bucket, you may need to modify your CloudFormation template to reference the existing bucket instead of trying to create a new one.

3. Ensure that you're using the latest version of the CID CloudFormation template. The most recent template can be found at: https://aws-managed-cost-intelligence-dashboards.s3.amazonaws.com/cfn/cid-cfn.yml

4. Double-check that you have the necessary permissions in your master account to create all the resources required by the CID stack, including S3 buckets, IAM roles, and QuickSight resources.

5. If you're using the master account for both source and destination, make sure this aligns with your intended setup. Typically, the source account would be where your Cost and Usage Report (CUR) is generated, and the destination account is where you want to analyze the data.

If the issue persists after trying these steps, you may need to delete any existing stacks related to your CID deployment attempt and start fresh with the latest template and unique resource names.
Sources
Already exists in stack | AWS re:Post
Cost Intelligence Dashboard (CID) deployment error - access to the AWS-managed s3 bucket that has the required Lambda layer is being denied | AWS re:Post