AWS QnABot is a multi-channel, multi-language conversational interface (chatbot) that responds to your customer's questions, answers, and feedback. The solution allows you to deploy a fully functional chatbot across multiple channels including chat, voice, SMS and Amazon Alexa.
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?
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?