I need to know best practices for handling the data collected from a AWS QnABot for 2 years that is cost affective

Q&A
, ,
1

I need to know best practices for handling the data collected from a AWS QnABot

2

Hi @dconstantino and welcome to the Quick Sight community!
When mentioning that you’re looking for best practices for handling the data collected, could you be a bit more specific on what you’re looking to do with the data? Is this in more in reference to security or how to re-purpose the information/data that’s been collected?

Attached below is the QnaBot implementation guide for your review; it holds some best practices throughout so I would suggest that you review this but let us know if you have any further questions.

3

I have a client who wants to retain the data for 2 years and needs Quick Sight to access the data for leadership, so they can verify that QnABot is meeting their expectations for customer adoption. I suggest they keep S3 and Archive the year two data in Glacier, which means they will have to retrieve the year two data to view it in QS. I also know they have Power BI, and I suggest they pull the year two data into the DB that PBI uses, so they don’t have to worry about AWS services. In short it is a cost issues as the data consumption grows they need to make sure the cost of having the QnABot does not get out of control.