AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document and updated references to access URLs, domains, and console locations.
Security assessment
The changes are purely branding updates from 'Amazon Connect' to 'Connect Customer' without modifying security protocols, vulnerabilities, or configurations. No evidence of security vulnerability fixes or security incidents addressed.
Diff
diff --git a/connect/latest/adminguide/update-your-connect-domain.md b/connect/latest/adminguide/update-your-connect-domain.md index 98b551311..0b8622ef3 100644 --- a//connect/latest/adminguide/update-your-connect-domain.md +++ b//connect/latest/adminguide/update-your-connect-domain.md @@ -7 +7 @@ -Custom code and integrationsFirewall allow listAbout the Amazon Connect access URL and emergency loginPersonal settingsTransport Layer Security (TLS) +Custom code and integrationsFirewall allow listAbout the Connect Customer access URL and emergency loginPersonal settingsTransport Layer Security (TLS) @@ -9 +9 @@ Custom code and integrationsFirewall allow listAbout the Amazon Connect access U -# Update your Amazon Connect domain +# Update your Connect Customer domain @@ -11 +11 @@ Custom code and integrationsFirewall allow listAbout the Amazon Connect access U -Amazon Connect instances that were created before March 31, 2021, were given a domain that looks like this: +Connect Customer instances that were created before March 31, 2021, were given a domain that looks like this: @@ -29 +29 @@ In the near future we plan to automatically change any remaining old domains tha - * If you have any custom code, a connector, or a firewall, it is your responsibility to update all references to your Amazon Connect URL from your old domain to your new domain. + * If you have any custom code, a connector, or a firewall, it is your responsibility to update all references to your Connect Customer URL from your old domain to your new domain. @@ -60 +60 @@ Continue reading this topic if you use a firewall, SAML, or other connectors suc - * About the Amazon Connect access URL and emergency login + * About the Connect Customer access URL and emergency login @@ -71 +71 @@ Continue reading this topic if you use a firewall, SAML, or other connectors suc -If you have any customization that involves Amazon Connect, review its code and replace hard-coded references to the previous domain with the new domain. For example, if you have a custom Contact Control Panel (CCP) integration, it likely relies on embedded URLs. Following are tips for updating other types of integration. +If you have any customization that involves Connect Customer, review its code and replace hard-coded references to the previous domain with the new domain. For example, if you have a custom Contact Control Panel (CCP) integration, it likely relies on embedded URLs. Following are tips for updating other types of integration. @@ -75 +75 @@ If you have any customization that involves Amazon Connect, review its code and -If you use Active Directory to manage identity and have an [Amazon Connect managed or customer managed](./connect-identity-management.html) instance, then update [ccpUrl](https://github.com/amazon-connect/amazon-connect-streams#connectcoreinitccp) to the new domain. The next time a user accesses the CCP they will be prompted to login to the new domain (one time only). +If you use Active Directory to manage identity and have an [Connect Customer managed or customer managed](./connect-identity-management.html) instance, then update [ccpUrl](https://github.com/amazon-connect/amazon-connect-streams#connectcoreinitccp) to the new domain. The next time a user accesses the CCP they will be prompted to login to the new domain (one time only). @@ -81 +81 @@ If you use SAML 2.0 to manage identity, then do the following steps: - * Update `ccpUrl` in your [Amazon Connect Streams](https://github.com/amazon-connect/amazon-connect-streams#connectcoreinitccp) to the new domain ``your-instance-alias`.my.connect.aws/ccp-v2`. + * Update `ccpUrl` in your [Connect Customer Streams](https://github.com/amazon-connect/amazon-connect-streams#connectcoreinitccp) to the new domain ``your-instance-alias`.my.connect.aws/ccp-v2`. @@ -120 +120 @@ If you use Salesforce, Zendesk, ServiceNow, or other connectors: - 2. In your connector, go to the settings and update the Amazon Connect domain that is stored there. Follow the SAML tips if applicable. + 2. In your connector, go to the settings and update the Connect Customer domain that is stored there. Follow the SAML tips if applicable. @@ -136 +136 @@ Add the following new domains to your allowlist: -If you are testing or using the new sign-in experience, also add the following domains to your allowlist. For more information, see [Testing the new Amazon Connect sign-in experience](./new-signin-experience.html). +If you are testing or using the new sign-in experience, also add the following domains to your allowlist. For more information, see [Testing the new Connect Customer sign-in experience](./new-signin-experience.html). @@ -172 +172 @@ For more information about setting up your allowlist, see [Set up your network]( -## About the Amazon Connect access URL and emergency login +## About the Connect Customer access URL and emergency login @@ -174 +174 @@ For more information about setting up your allowlist, see [Set up your network]( -The Amazon Connect access URL and emergency login URLs will be updated in the AWS console after we complete the domain migration. Until that time, they will reflect the old domain. +The Connect Customer access URL and emergency login URLs will be updated in the AWS console after we complete the domain migration. Until that time, they will reflect the old domain. @@ -176 +176 @@ The Amazon Connect access URL and emergency login URLs will be updated in the AW -The following image shows the location of the access URL on the **Amazon Connect virtual contact center instances** page. Even if you have taken steps to update your domain, this URL will continue to show the old domain. The URL on this page will update automatically when old domain traffic starts to redirect to the new domain. Please **do not use this URL to log in** ; rather, communicate to your team the new URL that they should be using. +The following image shows the location of the access URL on the **Connect Customer virtual contact center instances** page. Even if you have taken steps to update your domain, this URL will continue to show the old domain. The URL on this page will update automatically when old domain traffic starts to redirect to the new domain. Please **do not use this URL to log in** ; rather, communicate to your team the new URL that they should be using. @@ -178 +178 @@ The following image shows the location of the access URL on the **Amazon Connect - + @@ -192 +192 @@ To ensure a seamless transition for your team, we encourage you to take steps to -If your agents are using [browsers that Amazon Connect supports](./connect-supported-browsers.html), there is no action for you. For example, if you are using the latest Chrome and Firefox versions, no action is needed. +If your agents are using [browsers that Connect Customer supports](./connect-supported-browsers.html), there is no action for you. For example, if you are using the latest Chrome and Firefox versions, no action is needed. @@ -206 +206 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Use an allowlist for integrated applications in Amazon Connect +Use an allowlist for integrated applications in Connect Customer