Multi tenancy and datasets & dashboards

We have a multi tenant architecture. I have read through the community about using Namespace/User groups to create a multi tenancy support, however I was not able to find anything related to dashboards and datasets.

Here is our backend setup

We work with mysql and each tenant has there own schema.

Tenant 1 - schema_1
Tenant 2 - schema_2

We want to do one of the following

  • Create a generic dashboard and based on certain values like Namespace/Usergroups/Tags/… connect to a different datasets with same table structures keeping same visuals

OR

  • Create a generic dataset and based on certain values like Namespace/Usergroups/Tags/… connect to a different schemas.

Is this possible in quicksight? If so how?

Hi @abhijith7, welcome to the QuickSight Community.

Simple answer – No, it’s not possible. Complex answer, you could try the below two documents using a combination of shared folders and namespaces.

Please review my post - click here

Then, also review this blog - click here

We hope this solution worked for you. Let us know if this is resolved. And if it is, please help the community by marking this answer as a “Solution.” (click the check box under the reply)

Thanks @Xclipse for your answer

Unfortunately the links you shared doesn’t solve my issue here. On the other hand, does quicksight support jinja templates (Jinja — Jinja Documentation (3.1.x)) or similar ones in Custom SQL?

Hi @abhijith7, thank you for letting us know. I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!”

Jinja is not support. At AWS, our roadmap is primarily driven by our customers. Your feedback helps us build a better service. We have tagged this as a feature request.