Lex V2 bot not visible in Amazon Connect, despite all configurations being correct.

Question

Hello everyone,

I'm facing a blocking issue where my Amazon Lex V2 bot is not appearing in the Amazon Connect contact flow dropdown. I've spent a lot of time troubleshooting and have ruled out all common issues. I'm hoping someone in the community has seen this before.

Here is what I have verified:
- **Region:** Both the Lex V2 bot and the Connect instance are in us-east-1 (N. Virginia).
- **Language:** The bot's language (English US) is enabled in the Connect instance settings.
- **Bot Type:** The Lex bot is confirmed to be voice-enabled ("Audio and text") and has the "Voice settings" section configured.
- **Deployment:** The bot has been successfully built, a numbered version (Version 1) has been created, and an alias (TestBotAlias) is correctly pointing to that numbered version, not the "Draft" version.

Despite all of this, the bot is still not visible. Does anyone have any ideas what could be causing this, beyond the standard troubleshooting steps? Could it be a hidden IAM policy issue?

Luis Moreno · Answer

Ensure that the bot has been properly associated with your Connect instance. In the AWS Console, open the Amazon Connect service, select your Connect instance, then open the "Flows" configuration from the left menu. Verify that your Lex V2 bot is listed under the "Amazon Lex" section. If not, then add it there.

Luis Moreno

answered 10 months ago

EXPERT

Matt Barbieri

reviewed 8 months ago

re:Post Agent · Answer

Based on your description, you've covered most of the common configuration issues, but there are a few additional areas to check that might explain why your Lex V2 bot isn't appearing in the Amazon Connect contact flow dropdown.

First, verify that Amazon Connect and the Amazon Lex bot are in the same AWS account. Cross-account access isn't supported for this integration - even though they can be in different regions, they must be within the same AWS account.

Next, check the IAM permissions. The service-linked role for your Connect instance needs proper permissions to access the Lex V2 bot. This could be a hidden IAM policy issue as you suggested.

Another thing to try is to disable and then re-enable Lex Bot Management in your Amazon Connect console settings. This sometimes refreshes the connection between the services and makes previously invisible bots appear.

Also, ensure that the bot has been properly associated with your Connect instance. In the Amazon Connect console, navigate to "Contact flows" and verify that your Lex V2 bot is listed under the "Amazon Lex" tab.

If you're using Amazon Q in Connect with your Lex bot, check for any configuration issues there, as integration problems can sometimes prevent the bot from appearing in Connect.

Finally, examine CloudWatch logs for both Connect and Lex to look for any error messages that might provide additional clues about why the integration isn't working properly.  
**Sources**  
[Lex and Connect | AWS re:Post](https://repost.aws/questions/QUK5K741pzR_uE5BPog1jcSQ/lex-and-connect)  
[Amazon Q in Connect Error: Invalid Bot Configuration: Amazon Lex could not access your Q In Connect Assistant. | AWS re:Post](https://repost.aws/questions/QUQ14UzTMTSJ2U2tqZe8bj8Q/amazon-q-in-connect-error-invalid-bot-configuration-amazon-lex-could-not-access-your-q-in-connect-assistant)  
[Lex v2 with Connect not working | AWS re:Post](https://repost.aws/questions/QUUrKknnvERbWf3Pq8c6PBcA/lex-v2-with-connect-not-working)

Lex V2 bot not visible in Amazon Connect, despite all configurations being correct.

Add your answer

Relevant content