AWS connect documentation change
Summary
Replaced 'Amazon Connect' with 'Connect Customer' in titles, instructions, and error messages. Updated SAML endpoint naming.
Security assessment
Purely a service name rebranding. Cross-region agent association functionality and security implications remain unchanged. No security vulnerabilities or features were addressed.
Diff
diff --git a/connect/latest/adminguide/associate-agents-across-regions.md b/connect/latest/adminguide/associate-agents-across-regions.md index 754e1255d..e3520f85e 100644 --- a//connect/latest/adminguide/associate-agents-across-regions.md +++ b//connect/latest/adminguide/associate-agents-across-regions.md @@ -9 +9 @@ ExamplesWhy an AssociateTrafficDistributionGroupUser call fails -# Associate agents to Amazon Connect instances across multiple AWS Regions +# Associate agents to Connect Customer instances across multiple AWS Regions @@ -13 +13 @@ To allow your agents to sign-in to both AWS Regions and process contacts from ei - 1. If you have not yet set up a traffic distribution group, do so now. For instructions, see [Create traffic distribution groups for your Amazon Connect instance](./setup-traffic-distribution-groups.html). + 1. If you have not yet set up a traffic distribution group, do so now. For instructions, see [Create traffic distribution groups for your Connect Customer instance](./setup-traffic-distribution-groups.html). @@ -65 +65 @@ An [AssociateTrafficDistributionGroupUser](https://docs.aws.amazon.com/connect/l - 3. The `user-id `UUID`` is not a user from the source Amazon Connect instance. + 3. The `user-id `UUID`` is not a user from the source Connect Customer instance. @@ -76 +76 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Integrate your IdP with an Amazon Connect Global Resiliency SAML sign in endpoint +Integrate your IdP with an Connect Customer Global Resiliency SAML sign in endpoint