Migrating QuickSight dashboards from one AWS account to another

To handle QuickSight analyses that are larger than 1MB when migrating dashboards between AWS accounts using CloudFormation, you can use the following approach:

1. Instead of including the large template directly in the CloudFormation stack creation command, upload the template file to an Amazon S3 bucket.

2. Use the --template-url parameter in your create-stack command, pointing to the S3 URL of your template, rather than using --template-body.

Here's how you can modify your process:

1. Upload your large template file to an S3 bucket in your account.

2. Use the S3 Object URL in your CloudFormation stack creation command. The command would look something like this:

   aws cloudformation create-stack --stack-name YourStackName --template-url https://YOURBUCKETNAME.s3.amazonaws.com/YourTemplateName.json
   

This method allows you to bypass the 51,200 bytes (approximately 51KB) limit for inline templates and instead use templates up to 1MB in size stored in S3.

For templates larger than 1MB, you may need to consider breaking down your QuickSight assets into smaller, more manageable pieces. You could create multiple stacks, each handling a subset of your QuickSight resources, and then use nested stacks or cross-stack references to link them together.

Alternatively, you might want to explore using the QUICKSIGHT_JSON export format instead of CLOUDFORMATION_JSON. The QUICKSIGHT_JSON format allows for exporting assets as a single file with a .qs extension, which can handle larger asset bundles more easily. This format is particularly beneficial for managing QuickSight assets like dashboards due to its simplicity, speed, and version control capabilities.

Remember to ensure that your IAM roles have the necessary permissions to access the S3 bucket where you store your templates.
Sources
Choosing between the two export options of the Amazon QuickSight asset deployment APIs | AWS Business Intelligence Blog