AWS Quicksight Export Import Bundle APIs

Yes, you can use the same bundle.qs file and only update the data source details in the override parameters without affecting your existing dataset, analysis, and dashboard resources.

When using the StartAssetBundleImportJob API, you can specify override parameters specifically for the data source credentials and connection details. This allows you to point to your new Redshift cluster and VPC configuration while maintaining the structure and relationships of your other QuickSight assets.

In your override parameters, you'll need to include:

• DataSourceCredentials containing the credentials for your new Redshift cluster
• The DataSourceId, which should match the original DataSourceId from your source account (you may need to add a prefix like "Imported-" if you used one in your initial import)
• VPC connection details if your Redshift cluster is in a private VPC

It's important to note that when you run the import job with these overrides, you're only updating the data source configuration. The dataset, analysis, and dashboard that depend on this data source will continue to work with the updated data source as long as the schema and table structures remain compatible.

If you encounter an error like "DataSourceCredentials field is incorrectly set," double-check that your DataSourceId in the override parameters matches exactly what was used in your original import (including any prefixes).
Sources
Amazon QuickSight asset deployments using AssetBundle Export and Import APIs - Private Datasource Guidelines | AWS re:Post
Asset bundle import operations - Amazon QuickSight
Automate Deployment of Amazon QuickSight Assets with AWS Step Functions and QuickSight Asset Bundle APIs | AWS Partner Network (APN) Blog