I am implementing an automated way to deploy QuickSight assets within the same account and between accounts and I need your suggestion/recommendation.
Case:
Data Developers work in Data source/Data set/Schedule/Analysis/Dashboard. Once they are done, I need to replicate the same analysis/dashboard for all our different test clients. In other words, I need to "duplicate the analysis and dashboard pointing to different data set/sources.
My failed solution:
Create an export bundle for the analysis and dashboard and then import it for each test client. It did not work as analysis/dashboard in the bundle has a UUID it was just updating the same assets with the override data set/sources.
Question #1:
Is there a way to use the QS API to change the analysis/dashboard in a bundle? or do I need to programmatically unzip/change/zip and then import?
Question #2:
Are the bundle the right way to do it? or should I use something else such as a template? – which makes me wonder when should I use one versus the other?
Hi @jjluna,
The QS API is the method used for moving assets across AWS accounts and/or duplicating within the same account. Depending on your appetite for coding, this may be more work than you bargain for, but will give you ultimate flexibility for your use case. You can check out an old blog on how to do this here …Migrate Amazon QuickSight across AWS accounts | AWS Big Data Blog. This post uses QuickSight Templates as you reference in Question #2. I should mentioned this predates the introduction of QuickSight asset bundle operations now available in the QS API. You can find additional posts on this topic on the internet and references on this community site as well.
If coding isn’t your forte, our company has developed a solution - OverSight for Amazon QuickSight which is available on AWS Marketplace. It provides a non-coding approach to managing and deploying QuickSight assets across AWS Accounts using a web-based interface.
Full Disclosure: I’m sharing this in the spirit of providing options for your consideration, but by no means am I representing this as the “recommended way”. The value proposition of OverSight is for QuickSight development users & teams that want to focus their time and efforts on QuickSight development, rather than hand-coding DevOps supports.
Best of luck!
Thank you @gdiwx , appreciated the information you shared. I am comfortable coding, I just do not want to code something that is already available.
Do you know if it is possible to manipulate the UUID of the exported bundle asset using the QS APIs? or it is something after the export that has to be done?
Hi @jjluna,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.