AWS connect documentation change
Summary
Renamed 'Amazon Connect Customer Profiles' to 'Connect Customer Customer Profiles' throughout the document, including section headers, instructions, image captions, and link references. Added a duplicate 'Customer' in all rebranded references.
Security assessment
Changes are purely branding/naming updates with no security implications. The existing security recommendation about confused deputy prevention remains unmodified.
Diff
diff --git a/connect/latest/adminguide/enable-identity-resolution.md b/connect/latest/adminguide/enable-identity-resolution.md index 4048c72cf..18b2e1522 100644 --- a//connect/latest/adminguide/enable-identity-resolution.md +++ b//connect/latest/adminguide/enable-identity-resolution.md @@ -7 +7 @@ -# Enable Identity Resolution for your Amazon Connect Customer Profiles domain +# Enable Identity Resolution for your Connect Customer Customer Profiles domain @@ -24 +24 @@ After you enable Identity Resolution you'll see the option to [create consolidat - 1. You must have a Customer Profiles domain enabled for your instance. For instructions, see [Enable Customer Profiles for your Amazon Connect instance](./enable-customer-profiles.html). + 1. You must have a Customer Profiles domain enabled for your instance. For instructions, see [Enable Customer Profiles for your Connect Customer instance](./enable-customer-profiles.html). @@ -30 +30 @@ After you enable Identity Resolution you'll see the option to [create consolidat - + @@ -34 +34 @@ After you enable Identity Resolution you'll see the option to [create consolidat - + @@ -46 +46 @@ If you auto-enable merges, you will not receive matched profile IDs. -We recommend applying a policy to prevent a confused deputy security issue. For more information and a sample policy, see [Amazon Connect Customer Profiles cross-service confused deputy prevention](./cross-service-confused-deputy-prevention.html#customer-profiles-cross-service). +We recommend applying a policy to prevent a confused deputy security issue. For more information and a sample policy, see [Connect Customer Customer Profiles cross-service confused deputy prevention](./cross-service-confused-deputy-prevention.html#customer-profiles-cross-service). @@ -48 +48 @@ We recommend applying a policy to prevent a confused deputy security issue. For - 7. When done, choose **Enable Identity Resolution**. Both rule-based matching and ML-based matching are enabled after you enable Identity Resolution. You can disable one of them or both from the Identity Resolution page. For more information, see [Disable Identity Resolution in Amazon Connect Customer Profiles](./disable-identity-resolution.html). + 7. When done, choose **Enable Identity Resolution**. Both rule-based matching and ML-based matching are enabled after you enable Identity Resolution. You can disable one of them or both from the Identity Resolution page. For more information, see [Disable Identity Resolution in Connect Customer Customer Profiles](./disable-identity-resolution.html). @@ -64 +64 @@ Before running an Identity Resolution Job for the first time on a new Customer P - 2. You may want to set up consolidation criteria for auto-merging matching profiles. If so, see [Set up consolidation criteria for Identity Resolution in Amazon Connect](./create-consolidation-criteria.html). + 2. You may want to set up consolidation criteria for auto-merging matching profiles. If so, see [Set up consolidation criteria for Identity Resolution in Connect Customer](./create-consolidation-criteria.html).