AWS connect documentation change
Summary
Renamed 'Amazon Connect Cases' to 'Connect Customer Cases' and updated all related console/instance references throughout the document
Security assessment
Changes are purely branding/naming updates without any security implications. No vulnerabilities, security controls, or security features are mentioned or modified. IAM permissions remain unchanged except for naming consistency.
Diff
diff --git a/connect/latest/adminguide/enable-cases.md b/connect/latest/adminguide/enable-cases.md index f72b4cbd7..bde181a7d 100644 --- a//connect/latest/adminguide/enable-cases.md +++ b//connect/latest/adminguide/enable-cases.md @@ -9 +9 @@ RequirementsHow to enable CasesNext steps -# Enable Cases using the Amazon Connect console +# Enable Cases using the Connect Customer console @@ -11 +11 @@ RequirementsHow to enable CasesNext steps -This topic explains how to enable Amazon Connect Cases using the Amazon Connect console. To use the API, see [Amazon Connect Cases API Reference](https://docs.aws.amazon.com/cases/latest/APIReference/Welcome.html). +This topic explains how to enable Connect Customer Cases using the Connect Customer console. To use the API, see [Connect Customer Cases API Reference](https://docs.aws.amazon.com/cases/latest/APIReference/Welcome.html). @@ -15 +15 @@ This topic explains how to enable Amazon Connect Cases using the Amazon Connect -A case is always associated with a customer profile. You must have Customer Profiles enabled. Check your instance settings in the Amazon Connect console, and if a Customer Profiles domain does not yet exist, see [Enable Customer Profiles for your Amazon Connect instance](./enable-customer-profiles.html). +A case is always associated with a customer profile. You must have Customer Profiles enabled. Check your instance settings in the Connect Customer console, and if a Customer Profiles domain does not yet exist, see [Enable Customer Profiles for your Connect Customer instance](./enable-customer-profiles.html). @@ -19 +19 @@ A case is always associated with a customer profile. You must have Customer Prof -If you're using custom IAM policies to manage access to the Amazon Connect Cases, your users need the following IAM permissions to onboard to Cases using the Amazon Connect console: +If you're using custom IAM policies to manage access to the Connect Customer Cases, your users need the following IAM permissions to onboard to Cases using the Connect Customer console: @@ -40 +40 @@ If you're using custom IAM policies to manage access to the Amazon Connect Cases -For more information, see [Required permissions for using custom IAM policies to manage Amazon Connect Cases](./required-permissions-iam-cases.html). +For more information, see [Required permissions for using custom IAM policies to manage Connect Customer Cases](./required-permissions-iam-cases.html). @@ -42 +42 @@ For more information, see [Required permissions for using custom IAM policies to -## How to enable Amazon Connect Cases +## How to enable Connect Customer Cases @@ -44 +44 @@ For more information, see [Required permissions for using custom IAM policies to - 1. Open the Amazon Connect console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). + 1. Open the Connect Customer console at [https://console.aws.amazon.com/connect/](https://console.aws.amazon.com/connect/). @@ -46 +46 @@ For more information, see [Required permissions for using custom IAM policies to - 2. On the instances page, choose the instance alias. The instance alias is also your **instance name** , which appears in your Amazon Connect URL. The following image shows the **Amazon Connect virtual contact center instances** page, with a box around the instance alias. + 2. On the instances page, choose the instance alias. The instance alias is also your **instance name** , which appears in your Connect Customer URL. The following image shows the **Connect Customer virtual contact center instances** page, with a box around the instance alias. @@ -48 +48 @@ For more information, see [Required permissions for using custom IAM policies to - + @@ -79 +79 @@ After your cases domain is created, do the following: - 4. Optionally, [enable attachments](./enable-attachments.html) across your Amazon Connect instance. This step allows your agents to upload files to cases. For more information on the Files API, see the [StartAttachedFileUpload](https://docs.aws.amazon.com/connect/latest/APIReference/API_StartAttachedFileUpload.html) API documentation. + 4. Optionally, [enable attachments](./enable-attachments.html) across your Connect Customer instance. This step allows your agents to upload files to cases. For more information on the Files API, see the [StartAttachedFileUpload](https://docs.aws.amazon.com/connect/latest/APIReference/API_StartAttachedFileUpload.html) API documentation. @@ -83 +83 @@ After your cases domain is created, do the following: -Ensure that you have the `cases:CreateRelatedItem ` permission for your IAM entity. For more information on Cases permissions, see [Actions, resources, and condition keys for Amazon Connect Cases](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnectcases.html). +Ensure that you have the `cases:CreateRelatedItem ` permission for your IAM entity. For more information on Cases permissions, see [Actions, resources, and condition keys for Connect Customer Cases](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnectcases.html).