Troubleshooting AppInstanceBots configured with Amazon Lex V2 bots for Amazon Chime SDK messaging

The Amazon Chime SDK messaging delivers Amazon EventBridge events when an error prevents it from invoking the Amazon Lex V2 bot. For more information about setting up rules and configuring notification targets, refer to Getting started with Amazon EventBridge in the Amazon EventBridge User Guide.

If you receive EventBridge events in AWS CloudWatch Logs, you can use AWS CloudWatch Logs Insights to query EventBridge events based on the Amazon Chime SDK messaging detail-type. The failureReason lists the cause of the failure.

The following example shows a typical query.

fields @timestamp, @message
| filter `detail-type` = "Chime Messaging AppInstanceBot Lex Failure"
| sort @timestamp desc

If Amazon Chime SDK Messaging can invoke your Amazon Lex V2 bot, the SDK sends CONTROL messages with an error message.

For an AppInstanceBot to invoke an Amazon Lex V2 Bot, the Amazon Chime SDK messaging service principal must have permission to invoke the Amazon Lex V2 Bot resource. Also, ensure the AWS:SourceArn of the resource policy condition matches the ARN of the AppInstanceBot.

For more information about configuring an AppInstanceBot to invoke an Amazon Lex V2 bot, refer to Creating an Amazon Lex V2 bot for Amazon Chime SDK messaging, earlier in this section.

Amazon Lex has a service quota for the maximum number of concurrent text-mode conversations per bot alias. You can contact the Amazon Lex service team for quota increases. For more information, refer to Amazon Lex guidelines and quotas in the Amazon Lex Developer Guide.