We have multiple AWS accounts. Do i set up quicksight on every account or just on the master payer account?

Question & Answer
,
1

We have multiple AWS accounts. Do i set up quicksight on every account or just on the master payer account?

1 Like
2

Hello @othniel14, welcome to the QuickSight community!

The answer to this depends on what you are hoping to accomplish. If you have databases in each of the AWS accounts that need to be utilized, you can establish connections across AWS accounts to bring the data into your main AWS account. I can link some documentation below, but it is specifically for RDS and Redshift:

I think the ideal situation would be to build all in a single account if that works for you, unless you are wanting to split up your resources in Dev, QA, and Prod for testing purposes. Even then, if you are embedding, you can deploy them in those instances and test them from a single account. Let me know if this helps. If you provide some more information about how you want to utilize QuickSight, I can try to guide you further.

1 Like
3

Hi @DylanM ,

We have an AWS multi account structure. We have over 30 linked accounts and 1 Master Payer account.

We would love to have dashboards socialized in the Master-payer which showcases reports for the various linked accounts as opposed to logging into each linked account to view dashboards.

We would like to build Dashboard for a wide variety of services including but not limited to compute, storage, networking etc.

We are typically looking to have quicksight cloud intelligence dashboards operate like how Cost explorer operates at the Master payer account level.

1 Like
4

Related to this question is how we can support different identity regions for GDPR / Data Residency requirements. Would we need separate AWS accounts each with QuickSight enabled but assigned to a different identity region to support EU-based user registry?

Currently our QS accounts use us-east-1 as the identity region, but I am looking to understand what would be needed for supporting EU or Canada based customers who do not want their information stored on US-based servers

1 Like
5

Hello @othniel14 and @bkasen, I am working on setting up one of these dashboards on my team’s Master Payer account to see what the options are. I’ll get back to you in a bit with some more information. We had run one of these on the legacy version before they updated the CUR dashboard and it did link all of our other account information since all of our billing is managed from the main account, so I want to make sure this one works the same before I provide more information.

6

Thanks @DylanM. This article I found suggests that likely we’ll need separate AWS accounts and separate QuickSight accounts with a specified region that is not the default us-east-1:

7

Hello @bkasen, I see, yeah if the accounts outside of the payer accounts are in different regions, then it is likely you will need to make more than 1. Based on my internal testing though, it does look like the secondary accounts within us-east-1 are being referenced when running the CUR dashboard from our payer account. Maybe that would at least allow you to make less QuickSight accounts?

8

Thanks @DylanM - I spoke to our QuickSight account team. We will need to create a separate AWS account so we can identify a different identity region in a separate QuickSight account, to ensure user registration is done within the desired, non-us identity region.

1 Like
9

Hello @bkasen, I appreciate the follow-up information. Thanks for letting us know.

1 Like