- Newest
- Most votes
- Most comments
The issue typically arises due to a misconfiguration or permissions issue within the integration between Amazon Connect and Amazon Lex.
Here are the steps that have been successful for resolving this issue:
-
Disable and Re-enable Lex Bot Management in Amazon Connect: Navigate to the Amazon Connect Console. Under the Lex Bot settings, disable and then re-enable the Lex Bot Management feature.
-
Disable and Re-enable Bot Analytics and Transcripts: Similarly, disable and then re-enable the Bot Analytics and Transcripts setting in Amazon Connect.
-
Test: After performing the above steps, conduct a test to confirm the issue has been resolved.
answered 2 years ago
After going to amazon connect console, you need to click flows then you can continue to the lex bot settings about midway down the page.
The error you're encountering suggests that there's a permissions issue preventing Amazon Lex from accessing your Amazon Q in Connect Assistant. This is likely due to the Service Linked Role (SLR) for Amazon Lex V2 bots not having the necessary permissions to interact with Amazon Q in Connect.
To resolve this issue, you should try the following steps:
-
Ensure that Amazon Q in Connect is properly enabled for your Amazon Connect instance.
-
Verify that you've correctly set up the AMAZON.QinConnectIntent in your bot configuration. Make sure you've selected the correct Amazon Resource Name (ARN) for your Amazon Q in Connect assistant when enabling this intent.
-
If you're using a custom IAM role for your bot instead of the default Service Linked Role, you'll need to manually add the required permissions. The necessary permissions include:
- wisdom:CreateSession
- wisdom:GetAssistant
- wisdom:SendMessage
- wisdom:GetNextMessage
-
If you're using the default Service Linked Role (which seems to be the case based on the error message), you may need to recreate the bot or update it to trigger a refresh of the SLR permissions. Sometimes, the automatic update of the SLR doesn't occur immediately when new features are added.
-
Double-check that your Amazon Q in Connect domain is in the same AWS Region as your Amazon Lex V2 bot.
-
Ensure that your AWS account has the necessary permissions to use Amazon Q in Connect and that there are no service control policies (SCPs) restricting access.
If these steps don't resolve the issue, you may need to contact AWS Support for further assistance, as they can help diagnose any account-specific issues or permissions problems that might be preventing the proper configuration of Amazon Q in Connect with your Lex bot.
Sources
AMAZON.QinConnectIntent - Amazon Lex
Create an Amazon Q in Connect intent from an Amazon Connect instance - Amazon Connect
Getting started with AWS connect AmazonQ | AWS re:Post
answered 2 years ago
Tried #4 by updating the bot to see if the service linked role will be updated but it hasn't been updated.
Tried #3 but there is no option to specify a custom role for the bot instead of the default service linked role.
We found the issue for this. Service linked Role needs to be re-enabled and this seems like a known issue.
Disable and Enable the flag. " Enable Lex Bot Management in Amazon Connect Make your bots visible and editable. Customize additional capabilities within security profiles of your instance."
100% works.
answered 6 months ago
Relevant content
asked 2 years ago
asked a year ago
I'm also experiencing the same issue with Amazon Q in Connect integration. I’ve enabled the “Amazon Q in Connect” toggle while creating the Lex bot, but when I test it in the Lex console, I get the following error:
Invalid Bot Configuration: Amazon Lex could not access your Q In Connect Assistant.
CloudTrail shows an access issue:
User: arn:aws:sts::xyz:assumed-role/AWSServiceRoleForLexV2Bots_AmazonConnect_xyz/... is not authorized to perform: wisdom:CreateSession on resource: arn:aws:wisdom:region:account-id:assistant/...
I noticed that the service-linked role AWSServiceRoleForLexV2Bots_AmazonConnect_* doesn't have permissions to call wisdom:CreateSession, and since it's a service-linked role, it's not editable through IAM.
Also tried using the bot in a Connect flow via “Get Customer Input” and it fails there too.
Would appreciate any guidance or workaround from anyone who’s resolved this. Seems like either a missing policy or a misconfigured service role that Lex needs to talk to Amazon Q (Wisdom). AWS documentation doesn’t currently provide a clear solution for this.