AWS connect documentation change
Summary
Renamed 'Amazon Connect Cases' to 'Connect Customer Cases' throughout the document. Updated console references from 'Amazon Connect console' to 'Connect Customer console'. Updated authorization references from Amazon Connect to Connect Customer.
Security assessment
Changes are branding/naming updates only. No security permissions, policies, or vulnerabilities are modified. The IAM permission requirements remain unchanged.
Diff
diff --git a/connect/latest/adminguide/required-permissions-iam-cases.md b/connect/latest/adminguide/required-permissions-iam-cases.md index f791811c7..8e89f7ff3 100644 --- a//connect/latest/adminguide/required-permissions-iam-cases.md +++ b//connect/latest/adminguide/required-permissions-iam-cases.md @@ -9 +9 @@ View Cases domain detailsOnboard to Cases -# Required permissions for using custom IAM policies to manage Amazon Connect Cases +# Required permissions for using custom IAM policies to manage Connect Customer Cases @@ -11 +11 @@ View Cases domain detailsOnboard to Cases -If you're using custom IAM policies to manage access to the Amazon Connect Cases, your users need some or all of the permissions listed in this article, depending on the tasks they need to do. +If you're using custom IAM policies to manage access to the Connect Customer Cases, your users need some or all of the permissions listed in this article, depending on the tasks they need to do. @@ -15 +15 @@ If you're using custom IAM policies to manage access to the Amazon Connect Cases -There are two options for granting users IAM permissions to view Cases domain details on the Amazon Connect console. +There are two options for granting users IAM permissions to view Cases domain details on the Connect Customer console. @@ -19 +19 @@ There are two options for granting users IAM permissions to view Cases domain de -To view Cases domain details in the Amazon Connect console, users must have the following IAM permissions: +To view Cases domain details in the Connect Customer console, users must have the following IAM permissions: @@ -77 +77 @@ Note the following: - * `connect:ListIntegrationAssociations` action supports the `instance` resource type. See the table in [Actions defined by Amazon Connect](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnect.html#amazonconnect-actions-as-permissions). + * `connect:ListIntegrationAssociations` action supports the `instance` resource type. See the table in [Actions defined by Connect Customer](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnect.html#amazonconnect-actions-as-permissions). @@ -82 +82 @@ Note the following: -### Option 2: Update the existing Amazon Connect policy with `cases:GetDomain` and `profile:SearchProfiles` +### Option 2: Update the existing Connect Customer policy with `cases:GetDomain` and `profile:SearchProfiles` @@ -110 +110 @@ JSON -There are two options for granting users IAM permissions to onboard to Cases using the Amazon Connect console. +There are two options for granting users IAM permissions to onboard to Cases using the Connect Customer console. @@ -114 +114 @@ There are two options for granting users IAM permissions to onboard to Cases usi -To onboard to Cases by using the Amazon Connect console, users must have the following IAM permissions: +To onboard to Cases by using the Connect Customer console, users must have the following IAM permissions: @@ -213 +213 @@ Note the following: - * You can scope the permissions to specific Amazon Connect tasks by using the information in [Actions, resources, and condition keys for Amazon Connect](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnect.html). + * You can scope the permissions to specific Connect Customer tasks by using the information in [Actions, resources, and condition keys for Connect Customer](https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonconnect.html).