Why can’t I see any bots or aliases in Architect after I activate my Lex or Lex V2 integration?

Make sure that a Lex or Lex V2 bot has been created in the AWS console and received an alias.
Verify your AWS account. If you configured separate test and production accounts, be sure that you check for the bots in the correct account.
Verify that the IAM role has the correct permissions. For more information, see Troubleshoot Amazon Lex integrations.
For Lex V2, confirm that your bots were created in the correct AWS region. For example, us-east-1 for US, eu-west-1 for EU. For Lex V2, make sure that your integration’s advanced configuration is either {}, or that you include the region in which the bots are associated. For more information, see Configure and activate the Lex V2 integration in Genesys Cloud.

[NEXT] Was this article helpful?

Get user feedback about articles.

Make sure that a Lex or Lex V2 bot has been created in the AWS console and received an alias.
Verify your AWS account. If you configured separate test and production accounts, be sure that you check for the bots in the correct account.
Verify that the IAM role has the correct permissions. For more information, see Troubleshoot Amazon Lex integrations.
For Lex V2, confirm that your bots were created in the correct AWS region. For example, us-east-1 for US, eu-west-1 for EU. For Lex V2, make sure that your integration’s advanced configuration is either {}, or that you include the region in which the bots are associated. For more information, see Configure and activate the Lex V2 integration in Genesys Cloud.

Get user feedback about articles.