AWS lexv2 documentation change
Summary
Updated documentation to standardize naming from 'QInConnect' to 'QinConnect' and removed AMAZON.BedrockAgentIntent from incompatibility list
Security assessment
Changes are primarily capitalization/naming consistency (QInConnect → QinConnect) and removing a deprecated/irrelevant intent (BedrockAgentIntent) from compatibility notes. No security vulnerabilities, mitigations, or new security features are mentioned. Permission requirements for IAM roles/SLRs remain unchanged except for naming alignment.
Diff
diff --git a/lexv2/latest/dg/built-in-intent-qinconnect.md b/lexv2/latest/dg/built-in-intent-qinconnect.md index aef1af9c7..4e98d16fe 100644 --- a//lexv2/latest/dg/built-in-intent-qinconnect.md +++ b//lexv2/latest/dg/built-in-intent-qinconnect.md @@ -18 +18 @@ To use generative AI capabilities using Amazon Q In Connect, you must complete t -AMAZON.QInConnectIntent responds to customer questions by using the LLM-enhanced evolution of Amazon Connect Wisdom that delivers real-time recommendations to help contact center customers and agents resolve customer issues quickly and accurately. This intent is activated when an utterance is not classified into any of the other intents present in the bot. Note that this intent will not be activated for missed utterances when eliciting a slot value. Once recognized, the AMAZON.QInConnectIntent, uses the specified Q In Connect domain to search the configured knowledge base and respond to the customer question. +AMAZON.QinConnectIntent responds to customer questions by using the LLM-enhanced evolution of Amazon Connect Wisdom that delivers real-time recommendations to help contact center customers and agents resolve customer issues quickly and accurately. This intent is activated when an utterance is not classified into any of the other intents present in the bot. Note that this intent will not be activated for missed utterances when eliciting a slot value. Once recognized, the AMAZON.QinConnectIntent, uses the specified Q in Connect domain to search the configured knowledge base and respond to the customer question. @@ -22 +22 @@ AMAZON.QInConnectIntent responds to customer questions by using the LLM-enhanced - * You cannot use AMAZON.QInConnectIntent along with AMAZON.QnAIntent or AMAZON.BedrockAgentIntent intents, in the same bot locale. + * You cannot use AMAZON.QinConnectIntent along with AMAZON.QnAIntent in the same bot locale. @@ -36 +36 @@ If you select this intent, you need to configure the following fields and then s -The responses from the QInConnectIntent will be stored into the request attributes as shown below: +The responses from the QinConnectIntent will be stored into the request attributes as shown below: @@ -38 +38 @@ The responses from the QInConnectIntent will be stored into the request attribut - * `x-amz-lex:q-in-connect-response` – The response from QInConnectIntent to the question or utterance. + * `x-amz-lex:q-in-connect-response` – The response from QinConnectIntent to the question or utterance. @@ -43 +43 @@ The responses from the QInConnectIntent will be stored into the request attribut -**Session Attributes Returned from QInConnectIntent** +**Session Attributes Returned from QinConnectIntent** @@ -45 +45 @@ The responses from the QInConnectIntent will be stored into the request attribut -Interaction with the QInConnect intent provides additional data about conversation through session attributes. +Interaction with the QinConnect intent provides additional data about conversation through session attributes. @@ -49 +49 @@ Interaction with the QInConnect intent provides additional data about conversati - 2. `x-amz-lex:q-in-connect:conversation-status` – The current status of the conversation with QInConnect assistant or domain. There are three values possible for this status: + 2. `x-amz-lex:q-in-connect:conversation-status` – The current status of the conversation with QinConnect assistant or domain. There are three values possible for this status: @@ -70 +70 @@ Interaction with the QInConnect intent provides additional data about conversati -When a bot with QInConnectIntent is invoked during customer interactions driven by an Amazon Connect instance, your session arn needs to be created and passed from the Amazon Connect instance. To create a session, Amazon Connect Flows could be configured with Amazon Q In Connect step. +When a bot with QinConnectIntent is invoked during customer interactions driven by an Amazon Connect instance, your session arn needs to be created and passed from the Amazon Connect instance. To create a session, Amazon Connect Flows could be configured with Amazon Q in Connect step. @@ -74 +74 @@ When a bot with QInConnectIntent is invoked during customer interactions driven - * You cannot use AMAZON.QInConnectIntent along with intents without specific utterances such as AMAZON.QnAIntent, AMAZON.BedrockAgentIntent in the same bot locale. + * You cannot use AMAZON.QinConnectIntent along with intents without specific utterances such as AMAZON.QnAIntent, AMAZON.BedrockAgentIntent in the same bot locale. @@ -76 +76 @@ When a bot with QInConnectIntent is invoked during customer interactions driven - * When a bot with QInConnectIntent is invoked during a customer interactions driven by an Amazon Connect instance, your session arn needs to be created and passed from the Amazon Connect instance. To create a session, Amazon Connect Flows could be configured with Amazon Q In Connect step. + * When a bot with QinConnectIntent is invoked during a customer interactions driven by an Amazon Connect instance, your session arn needs to be created and passed from the Amazon Connect instance. To create a session, Amazon Connect Flows could be configured with Amazon Q In Connect step. @@ -78 +78 @@ When a bot with QInConnectIntent is invoked during customer interactions driven - * There can be no more than one AMAZON.QInConnectIntent per bot locale. + * There can be no more than one AMAZON.QinConnectIntent per bot locale. @@ -80 +80 @@ When a bot with QInConnectIntent is invoked during customer interactions driven - * The Amazon Q In Connect domain used with AMAZON.QInConnectIntent must be in the same AWS Region as the Amazon Lex V2 bot. + * The Amazon Q in Connect domain used with AMAZON.QinConnectIntent must be in the same AWS Region as the Amazon Lex V2 bot. @@ -87 +87 @@ When a bot with QInConnectIntent is invoked during customer interactions driven -If the QInConnect Intent is used in an Amazon Lex V2 bot, and the bot is using a Service Linked Role (SLR), the Amazon Lex V2 service has the permissions to update the appropriate policies on the role to integrate it with the Q In Connect assistant. If the bot is using a custom IAM role, then the user would need to manually add these permissions to their IAM role. +If the QinConnect Intent is used in an Amazon Lex V2 bot, and the bot is using a Service Linked Role (SLR), the Amazon Lex V2 service has the permissions to update the appropriate policies on the role to integrate it with the Q in Connect assistant. If the bot is using a custom IAM role, then the user would need to manually add these permissions to their IAM role. @@ -89 +89 @@ If the QInConnect Intent is used in an Amazon Lex V2 bot, and the bot is using a -The Service Linked Role will get updated with the following permissions if the QInConnect intent gets added. A new policy will be added for QInConnect access: +The Service Linked Role will get updated with the following permissions if the QinConnect intent gets added. A new policy will be added for QinConnect access: