Non-prod to prod or versioning for non self service model

Hi @pyi -

  1. You can only have one QuickSight instance per AWS account. A common approach is to have separate non-prod and prod AWS accounts.

  2. You can leverage QuickSight API/SDKs for both cross-account and same-account deployments. See example blog BIOps: Amazon QuickSight object migration and version control | AWS Big Data Blog

  3. One approach is to put nonprod (dev, test, uat) in one account and prod in another. You can use shared folders/user groups to segment the nonprod stages. Managing Dashboards/Analyses can be done completely through the UI but you’ll want to leverage the API for DataSets/DataSources. There is currently a limitation where you can’t switch a DataSet’s DataSource in the UI.

2 Likes