Is there an option for cross-account data source sharing?
Our case is that we want to author the analysis and dashboards in a single “author” QuickSight account, and then these reports would get deployed to many AWS accounts to be consumed. However, when designing reports, we need to design them against live data sets, which is where the data source sharing comes in.
We don’t want to share the database connection details cross-account. Just the ability to create data sets from a data source in another account.
Hi @royyung I think I have watched this workshop already. I don’t remember it talking about being able to share data sources across accounts. I’ll give it another scan then. Thanks.
hi @m0ltar , sorry, may be I get it wrong before. Do you mean account B dataset pointing to account A’s data source? If yes, QuickSight do not support this setup. The use case I mentioned is for deployment from Dev to Prod account. therefore, data source will be different in different accounts to provide an isolated environment between Dev and Prod. If the requirement is for multi-tenant architecture, we do have a feature called “Namespace” for user isolation in the same QuickSight account Embed multi-tenant analytics in applications with Amazon QuickSight | AWS Big Data Blog
Maybe there is another solution that can fit with our workflow.
Basically, we have a multi-tenant application, with an account-based tenancy. Each client has its own deployment of the ETL pipeline.
But the reports are the same across the accounts.
When we develop the reports, we need to work with the production data source, as we do not have real-world, representative data in our staging (QA) and/or the account where the QuickSight for authors is setup.
So what we want, is to be able to point the central QuickSight account, to any tenant account and be able to develop reports for them from a central account.
Hi, @m0ltar. We hope the responses from @DeepakS and @royyung helped you. Let us know if this is resolved. And if it is, please help the community by marking the answer as a “Solution”.