Thanks! 😀 🤝

Thank you for your inquiry, Curtis! I encourage following along with this resource, which goes along with this video, for a more in-depth understanding: go.aws/3AB8Z5Q. 🔗 This would also be an excellent opportunity to further expand on your question with our cloud experts on re:Post: go.aws/aws-repost. 📮 They can provide their expertise to address any technical questions that you may have. ☁️ I've also gathered a few additional links that I recommend looking into: go.aws/470c2jS & go.aws/4dA7m6P & go.aws/4fZsCEH. ⬅️ ^TE

Hi there, glad to see your interest in our video! 👀 I've got a couple resources for you, the first being one of our official docs, check it out: go.aws/4aSEDbD. ✅ Lastly, I'd recommend that you take a look at our re:Post: go.aws/aws-repost. If you like, you can post to and see posts from our industry experts. They have a lot of knowledge and may be able to help you out too. 💡 ^DC

Hello, 👋 these resources are a great starting point: go.aws/48ZqoQZ & go.aws/4cqR2FC. If you have further questions about capabilities related to your use case, you can reach out to our Sales team with this form: go.aws/4coEBde. If the phone number is there, they are available to hop on a call. Hope it's helpful! ^AD

These are great!

Great questions! These docs may have more info: go.aws/48zY87Z & go.aws/3RXbs0v. Additionally, our community of experts in re:Post might have further insight to your questions, feel free to reach out here: go.aws/aws-repost. 🖇️ ^LG

@@awssupport thanks but that first link wasn't relevant. It was about load balancing.

Sorry that wasn't quite right. I suggest reaching out in re:Post for additional advice and tutorials: go.aws/3RWITAo.^RS

Amazon Lex determines user intent based on the prompt (what Lex calls an utterance). Lex intents include statically defined intents and a fallback intent that sends the user prompt to the Bedrock FM if no other intents are identified. The Lambda handler instruments the logic for each intent. For static flows, Lex prompts the user for a series of slot values needed for intent fulfillment. User slot values are validated in the Lambda handler logic. If the user provided slot value is not considered valid, the Lambda handler logic routes the user input to the Bedrock FM then re-prompts for the slot value to continue static intent fulfillment. You can also switch intents by providing a user utterance that maps to another intent based on Amazon Lex NLU.

Hi there, thanks for the question. ❔ I am going to suggest checking out this: go.aws/4c6CwT6. It should help you get started with generative AI on AWS. Also, a good option is our re:Post. There you can view posts and post to some of our industry experts: go.aws/aws-repost. 🧠 ^DC

Kommunicate is only used to create the JavaScript plug-in that invokes the Amazon Lex RecognizeUtterance API. Customers will typically integrate Amazon Lex into their existing front ends using custom ReactJS chat components.

"Chain of thought" is intentionally used to described the LangChain conversational agent's prompt reasoning process in relationship to the FM. The action and observation steps are subsequently mentioned in relationship to the agent's available tooling to emphasize RAG capabilities in this example. You can lump these reasoning steps into a single ReAct "chain-of-thought-action-observation" workflow, however, that dilutes the focus on the agent's conversational prompting and action execution relative to LangChain's ReAct agent.