1 Answer
- Newest
- Most votes
- Most comments
0
Lex does not support returning voice utterances in API response. It only returns transcripts of the input audio.
For data analysis on voice utterances, you can enable Lex conversation logs to access user's voice utterances for data analysis. https://docs.aws.amazon.com/lexv2/latest/dg/conversation-logs-s3.html. The audio data gets stored in a customer specified S3 bucket, which can later be accessed using a Lambda function.
answered 2 years ago
Relevant content
- asked 2 years ago
- asked 5 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
swapandeepataws, would it be possible in the future for the Lex team to please return the S3 URL from the Lex bot CloudWatch logs to the response sent to Lambda via Lex codehook on each turn?
You can see in Lex logging output to CloudWatch (if turned on for conversation logs in Lex bot alias settings), those logs from Lex show the S3 utterance path. But that’s not passed from Lex to the Lambda codehook as info that we could use to “tie together” the utterance text transcript from the response JSON to its associated utterance S3 URL recording.
We know how to find the utterances in S3, but without the URL that ties to the text, we can’t “match them up” effectively in our custom app (they aren’t necessarily recorded in order to the bucket—they can be written “out of order”). We’d like to show the text utterance, and also hyperlink it to the associated S3 URL for the utterance it was related to. That way, the user could click on an utterance result in our custom app, and play the actual recording that was captured. Would be a great feature.
Is anything like that possible today? Or could a feature request be added to Lex to please pass on that S3 URL to the JSON response for use so we could leverage it?