Hindi Language Lex Bot Issue

It appears you're experiencing an integration issue between Amazon Connect and your Hindi language Lex bot. This is a common problem that can occur even when one language (in this case, English) is working correctly. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Language Attribute: Ensure you've correctly set the language attribute for Hindi in your Connect flow. Even if you've selected a Hindi voice in the 'set voice' block, you need to explicitly set the language attribute to the correct code for Hindi (which is 'hi-IN') in the flow component. This is a crucial step that's often overlooked.

2. Bot Configuration: Verify that your Lex bot is properly configured to support Hindi. Make sure you have intents, sample utterances, and responses set up for the Hindi language in your Lex bot.

3. Alias and Version: Double-check that the alias you're using in Connect points to a version of your bot that includes Hindi language support.

4. IAM Permissions: Ensure that the IAM role associated with your Connect instance has the necessary permissions to invoke the Lex V2 bot, specifically for the Hindi language version.

5. Resource Quotas: Verify that you haven't exceeded any resource quotas when associating the bot with Connect, particularly for multiple language support.

6. CloudWatch Logs: Examine the CloudWatch logs for both Connect and Lex to look for more detailed error messages that might provide additional clues about the cause of the 'BadRequestException' error.

7. Session ID: Ensure you're not using an excessively long session ID. Keep it under 64 characters, as longer session IDs can cause issues.

If you've verified all these points and are still experiencing issues, you may need to start with a simplified setup. Create a basic flow and bot configuration with minimal Hindi language support, then gradually add complexity to identify where the issue occurs. If the problem persists, it may be necessary to contact AWS support for more in-depth troubleshooting, as they can access more detailed logs and configuration information.
Sources
Lex v2 with Connect not working | AWS re:Post
Amazon Lex language integration failures in my Amazon Connect instance. | AWS re:Post
Amazon Lex API Call Fails: "Invalid Bot Configuration: Amazon Lex could not access your Amazon Bedrock Agent" | AWS re:Post

Hello,

This seems to suggest that there is an issue with the Lex bot itself.

I believe reviewing these few points are a good starting point to begin your troubleshooting:

1. Make sure you've correctly set the language attribute for Hindi in your Connect flow. Even if you've selected a Hindi voice in the 'set voice' block, you need to explicitly set the language attribute to the correct code for Hindi (which is 'hi-IN') in the flow component.

2. Verify that your Lex bot is properly configured to support Hindi. Make sure you have intents, sample utterances, and responses set up for the Hindi language in your Lex bot.

3. Double-check that the alias you're using in Connect points to a version of your bot that includes Hindi language support.

If none of these work, I would suggest reaching out to AWS Support for a deeper dive.