How to Properly Test Import in Quick Sight Without Deleting Existing Analysis?

Q&A
, , , , ,
1

I’m working on testing the import of Quick Sight assets, and I have the following setup in my account:

  • Analysis: Includes charts, tables, and filters
  • Datasets
  • Datasource
  • Shared folder
  • Group

Here are the steps I followed so far:

  • Created an analysis with charts, tables, and filters.
  • Ran the export job to capture the analysis and its dependencies, using the following command:
aws quicksight start-asset-bundle-export-job \ 
   --aws-account-id ACCOUNT-ID \ 
   --asset-bundle-export-job-id bundle-export-25-job-100bf5c8-8c55-4af5-83d7-7a51a9b77255 \ 
   --resource-arns arn:aws:quicksight:REGION:ACCOUNT-ID:analysis/100bf5c8-8c55-4af5-83d7-7a51a9b77255 \ 
   --include-all-dependencies \
   --include-permissions \
   --export-format QUICKSIGHT_JSON
  • Downloaded the exported assets and uploaded them to a dedicated S3 bucket in the target account.
  • Deleted all datasets and datasources.

How can I properly test the import in this scenario, considering that the analysis already exists in the target account? Since I can’t safely delete it (removing it only changes the status to “deleted” but doesn’t completely erase it), what steps should I follow to ensure a clean test of the import?

I’d appreciate any guidance on handling the presence of existing analyses when testing imports to avoid conflicts or overwrites.

2

Hi @maxim, have you tried to import the bundle in a different region?
If you do not want to have different account to manage the dev lifecycle, this idea can work for you usecase?

Andrea

3

@andrepgn hi, thank you for your interest in this topic.

Thank you for your suggestion. However, I prefer to conduct my testing in a single region to align with my development workflow. Testing in different regions or accounts can introduce variables that may not accurately reflect the environment I’ll be working in. Additionally, it’s not always obvious how analyses behave in Quick Sight—sometimes versions reset, and other unexpected complications can arise. I’m not confident that working in a different region won’t lead to unforeseen issues.

I’ve already tested from scratch by recreating a full Quick Sight account, which added unnecessary costs. That’s why I’m looking for a clear and straightforward option to test without complications from existing analyses, especially since I need to test several times for this import scenario.

4

Hi @maxim,
It’s been awhile since last communication took place on this thread, were you able to find a work around or were you still in need of further assistance?

If we do not hear back within the next 3 business days, I’ll close out this topic.

Thank you!