AWS connect documentation change
Summary
Updated all references from 'Amazon Connect' to 'Connect Customer' including titles, console references, and feature names
Security assessment
Changes are purely cosmetic branding updates. The SCP policy behavior explanation remains unchanged and doesn't introduce new security considerations. No security features or vulnerabilities are addressed.
Diff
diff --git a/connect/latest/adminguide/enable-bot-building.md b/connect/latest/adminguide/enable-bot-building.md index 9401d9bf3..98ff6a9d6 100644 --- a//connect/latest/adminguide/enable-bot-building.md +++ b//connect/latest/adminguide/enable-bot-building.md @@ -7 +7 @@ -# Enable bot building and analytics in Amazon Connect +# Enable bot building and analytics in Connect Customer @@ -9 +9 @@ -Complete the following steps to enable users to create Amazon Lex bots in the Amazon Connect admin website and view metrics about bot performance. +Complete the following steps to enable users to create Amazon Lex bots in the Connect Customer admin website and view metrics about bot performance. @@ -11 +11 @@ Complete the following steps to enable users to create Amazon Lex bots in the Am -Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect. +Users can not edit LEX V1 bots or cross-regional bots from within Connect Customer. @@ -13 +13 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect - 1. Open the [Amazon Connect console.](https://console.aws.amazon.com/connect/) + 1. Open the [Connect Customer console.](https://console.aws.amazon.com/connect/) @@ -15 +15 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect - 2. Select the Amazon Connect instance that you want to integrate with your Amazon Lex bot. + 2. Select the Connect Customer instance that you want to integrate with your Amazon Lex bot. @@ -17 +17 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect - + @@ -21 +21 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect - 4. Choose **Enable Lex Bot Management in Amazon Connect** and **Enable Bot Analytics and Transcripts in Amazon Connect** , and then **Save**. + 4. Choose **Enable Lex Bot Management in Connect Customer** and **Enable Bot Analytics and Transcripts in Connect Customer** , and then **Save**. @@ -23 +23 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect - + @@ -27 +27 @@ Users can not edit LEX V1 bots or cross-regional bots from within Amazon Connect -If you already have existing Service Control Policies (SCP) in place that block access to Lex, Amazon Connect respects those policies and does not enable the Bot Management and Analytics feature. However, if you put those SCP policies in place after you've already enabled this feature, they won't be respected. In that case, you'll need to disable this feature. +If you already have existing Service Control Policies (SCP) in place that block access to Lex, Connect Customer respects those policies and does not enable the Bot Management and Analytics feature. However, if you put those SCP policies in place after you've already enabled this feature, they won't be respected. In that case, you'll need to disable this feature. @@ -29 +29 @@ If you already have existing Service Control Policies (SCP) in place that block -Amazon Connect displays the service role and service linked role name it uses. uses Amazon Lex resource-based policies to make calls to your Amazon Lex bot. When you associate an Amazon Lex bot with your Amazon Connect instance, the resource-based policy on the bot is updated to give Amazon Connect permission to invoke the bot. +Connect Customer displays the service role and service linked role name it uses. uses Amazon Lex resource-based policies to make calls to your Amazon Lex bot. When you associate an Amazon Lex bot with your Connect Customer instance, the resource-based policy on the bot is updated to give Connect Customer permission to invoke the bot.