Ends in

$2 OFF ALL AWS, Azure, Google Cloud & Kubernetes Practice Exams!

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Professional Not lex but Comprehend? Reply To: Not lex but Comprehend?

  • Neil-TutorialsDojo

    January 16, 2024 at 5:52 pm

    Hi @Aparna-Bl, @ccatchings , @kaws8902

    Thank you for raising your question, aparna. Following up Kenneth’s response Amazon Lex is the preferred choice for recognizing caller intent based on voice input. Amazon Comprehend, on the other hand, is more suited for text-based input. In the context of receiving calls and creating contact flows, the voice-based capabilities of Amazon Lex make it the correct solution for this scenario.

    To kaws8902 and ccatchings, your concerns about SQS limitations for streaming audio data are valid. Thanks for pointing this out. In a call center setup where someone is talking directly to a Lex bot and getting immediate responses, you don’t really need SQS. Amazon Lex has its own API that you can use to facilitate the conversation between the caller and the bot. Though here’s how I imagine SQS can be used with Amazon Lex. Instead of putting the audio itself in the SQS message, we can store the audio somewhere like in Amazon S3, and just reference its URL in the message. Then, a Lambda function can pick up this message from SQS, process the audio file from S3, and subsequently invoke the Lex API for further actions.

    With all that said, we apologize for any confusion this question might have caused. We really appreciate your input and will make sure to refine and improve this question based on your feedback.