-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QnA bot multi tenancy #525
Labels
Comments
We are evaluating adding this to our 2024 roadmap. Will respond here with updates. |
Any movement on this? Also, is there a recommended way to to connect to existing Cognito User Pool, or existing OpenSearch domain? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, my team is considering using QnA bot in a multi tenancy context where we have multiple customers that need to be served by the same services, while only having the core bot data being unique for each customer.
My first thought is that kendra and opensearch should be unique per customer, whereas the rest of the services could be common.
Is there any good approach for doing this? Or should we stick to single tenant architecture?
The text was updated successfully, but these errors were encountered: