User Migration

Question & Answer
1

Can users of one QuickSight Account be migrated to another account.

@Sanjeeb2022 @Max @AnwarAli

3

Hi,

It’s not possible yet.

Cross region QS migration is possible using the API.

regards,
Naveed Ali

2 Likes
4

Hi @Sabiha - For each AWS account, there is ONLY one QuickSight account. If you want to migrate user from one account to another, essentially you have to create the user in another account. Now the complexity will come, how to provide the set permission to the dashboards in another account, this is something we can leverage custom program and quicksight API to do the same.

Note: Before user migration, you need to migrate all datasets, analysis and dashboards to the new account and @Naveed already provided the details for the same.

Tagging @Koushik_Muthanna @Kellie_Burton for their expert advise as well.

Regards - Sanjeeb

1 Like
5

Thank you @Naveed , so users have to be created separately :+1:

1 Like
6

Thank you @Sanjeeb2022 , if I have say 700 Quicksight registered Users, can I still use Capacity planning?

1 Like
7

Hi @Sabiha - It can be done by a custom script using QuickSight boto3 APIs and can be scale as well.

However a poc is require to prove this.

Regards - Sanjeeb

8

Capacity planning is done to reduce the cost of per reader and cost is calculated per session. Are you talking about the same?

9

Hi @Sabiha - Nope, I am provided the details on the migration solution. For capacity and cost, can we raise a ticket to AWS Customer support to get the details on cost as user base is very high and there should be some enterprise cost and saving as well.

Regards - Sanjeeb

1 Like
10

When we are migrating the Dashboards, Analysis, and Datasets from Account A to Account B, which data will be visualized on the dashboard (Account A’s or Account B’s). I want to see the new data of Account B, will this document “Migrate Amazon QuickSight across AWS accounts | Amazon Web Services” work in this scenario ???
@Sabiha @Sanjeeb2022

1 Like
11

Hi @shravya - Welcome to AWS QuickSight community and thanks for posting the question. This is an interesting question asked by you.You need to update the data sources with right connection and assume that data sources are updated in datasets, then it should show account B info :slight_smile: if all are data sources are same, ensure update the data set ID as per each data source, the ID is unique at account level unless you hard coded the id.

Regards - Sanjeeb

2 Likes
12

Thank you @Sanjeeb2022 :slight_smile:
A follow-up question, can we share dashboards across regions in the same account? If yes, how can we do that? A few inputs from you will be great :slight_smile:

1 Like
13

Hi @shravya - You can not share dashboard from region A and region B. However I believe you can extract a template and recreate the dashboard in region B ( like cross account).
See a sample link -

Hi @Koushik_Muthanna @Karthik_Tharmarajan @Naveed @David_Wong - Can you provide your opinion on this.

Regards - Sanjeeb

2 Likes
14

Thank you @Sanjeeb2022 and @Naveed for the quick response and pointing to the right resource.

I followed this documentation regarding migration - I am able to migrate the dashboard with the process given below!

My question is -
Migration is done right.

  1. Now if we made some updates to the dashboard that is in Dev environment and wanted to have the new updated dashboard in Test environment, do we need to follow the same steps again to get the updated dashboard in the Test environment?
  2. If yes for the 1st point, will it create different id for the same dashboard and will we be able to see the 2 dashboards with same name?
1 Like
15

Hi @shravya - Good to know that you are able to migrate the dashboard. If there is any change in the dashboard in DEV, you can follow the same process only difference in target you need to collect the dashboard ID ( as QuickSight always create a unique ID for each object) and update the dashboard instead of creating it. I never tried this option, but you can do a POC for the same.

Hi @Naveed @David_Wong and @Max - What is your feedback on this?

Regards - Sanjeeb

1 Like
16

Hi @shravya, @Sanjeeb2022,

When you use the UI to create a dashboard, a random id is generated but you can set your own dashboard id when you use the API. Since your DEV environment is in a different AWS account, I think you should be able to set your dashboard id in DEV and Prod to be the same. You’ll have to give it a try.

You can take a look at the new APIs that the QuickSight team just released this week. They may help with your migration.

3 Likes
17

Thanks @David_Wong for sharing this detail. On another note - we can always get the dashboard id from the describe dashboard and take that ID and update the details via update dashboard api, theoretically it should work.

Regards - Sanjeeb

2 Likes
18

@Sanjeeb2022 - Thank you so much. I will try that out and see the outcome.

1 Like
19

Thank you @David_Wong for sharing the blog. I will definitely take a look and try out a few things

1 Like
20

@Sanjeeb2022 I’ve never tried for dashboards but I tried for datasets and it didn’t work for me when I tried to use the API to change a randomly generated id to one of my choice. I think it makes sense that we can’t change it because it’s the unique identifier for the asset. There’s also no datasetId in the request body in the documentation.

3 Likes