How to maintain one SessionID or UserID for AWS Lex Bot

Question

Hey Folks,

I am currently working on a Lex automation that involves gathering the conversation logs from a Lex bot (V1). I notice that in my CloudWatch group, there is a log stream event created for each intent as the user interacts with the bot. The goal is to take the JSON data from each log stream and convert it into one file (I currently built and tested the code to do so). When a log stream is created in the log group, a Lambda function will be triggered to process the data. I realized a flaw; I noticed that each log stream has a different key. Within the JSON data, the SessionID and UserID tends to be different although it is one interaction. For me to be able to build this automation fully, I need to find a way to keep one of those values the same, unless there is another way to correlate the two separate log streams. Any thoughts to this?

Additional Information: I have also tried to adjust the Session Timeout time. I had it on 5 minutes and increased it to 10, this of course had no effect.

Answer

Hello,

Could you explain more on which API call you are making here that contains the different UserID and SessionID? You can also share sample JSON (while removing any sensitive information). This looks more of a limitation at the source of the logs rather than at the Log Group level. You can share more details for further insight.

How to maintain one SessionID or UserID for AWS Lex Bot

Relevant content