AWS connect documentation change
Summary
Rebranded 'Amazon Connect' to 'Connect Customer' throughout the documentation, including instance references and workspace names.
Security assessment
Changes are purely terminological rebranding with no security vulnerability fixes, security feature additions, or security-related explanations. No evidence of security impact.
Diff
diff --git a/connect/latest/adminguide/update-agents-across-regions.md b/connect/latest/adminguide/update-agents-across-regions.md index 6b7100e72..b472dfa66 100644 --- a//connect/latest/adminguide/update-agents-across-regions.md +++ b//connect/latest/adminguide/update-agents-across-regions.md @@ -9 +9 @@ RequirementsEnable both Regions during regular operationsHow to shift all teleph -# Update agent distribution in your Amazon Connect agent workspace across AWS Regions +# Update agent distribution in your Connect Customer agent workspace across AWS Regions @@ -21 +21 @@ After you have added agents to your traffic distribution group, use the [UpdateT -If an agent gets an error when they try to end a contact before shifting Regions, they need to refresh the agent workspace page. For more information, see [Set up Amazon Connect Agent Workspace to support agents shifting across AWS Regions](./setup-agentworkspace-switchover.html). +If an agent gets an error when they try to end a contact before shifting Regions, they need to refresh the agent workspace page. For more information, see [Set up Connect Customer Agent Workspace to support agents shifting across AWS Regions](./setup-agentworkspace-switchover.html). @@ -44 +44 @@ If the following requirements are not met, your [UpdateTrafficDistribution](http - 3. If you are changing the `SignInConfig` distribution, you can only do so for the default traffic distribution group. The default traffic distribution group is created when the replica Amazon Connect instance is created. See the `IsDefault` parameter in the [TrafficDistributionGroup](https://docs.aws.amazon.com/connect/latest/APIReference/API_TrafficDistributionGroup.html) data type. + 3. If you are changing the `SignInConfig` distribution, you can only do so for the default traffic distribution group. The default traffic distribution group is created when the replica Connect Customer instance is created. See the `IsDefault` parameter in the [TrafficDistributionGroup](https://docs.aws.amazon.com/connect/latest/APIReference/API_TrafficDistributionGroup.html) data type. @@ -103 +103 @@ This distribution controls only which Region of the sign-in server is used to fa -If the sign-in endpoint is not responsive during agent sign-in and your `SignInConfig` distribution is split across Regions, then you can resolve the errors by changing distribution to a single AWS Region. Or, if your `SignInConfig` is weighted on one Region and it isn't responsive, you can try shifting the `SignInConfig` to the disabled Region. Regardless of how your `SignInConfig` is configured, agents will still benefit from having a session active in both the source and replica Regions because they will attempt to sign into their Amazon Connect instance in both Regions. +If the sign-in endpoint is not responsive during agent sign-in and your `SignInConfig` distribution is split across Regions, then you can resolve the errors by changing distribution to a single AWS Region. Or, if your `SignInConfig` is weighted on one Region and it isn't responsive, you can try shifting the `SignInConfig` to the disabled Region. Regardless of how your `SignInConfig` is configured, agents will still benefit from having a session active in both the source and replica Regions because they will attempt to sign into their Connect Customer instance in both Regions.