AWS Security ChangesHomeSearch

AWS connect documentation change

Service: connect · 2026-05-19 · Documentation low

File: connect/latest/adminguide/setup-traffic-distribution-groups.md

Summary

Replaced 'facilitate' with 'help' in SignInConfig description

Security assessment

Minor wording change clarifying agent sign-in functionality. No modification to security controls or configurations.

Diff

diff --git a/connect/latest/adminguide/setup-traffic-distribution-groups.md b/connect/latest/adminguide/setup-traffic-distribution-groups.md
index 85786c6a2..12c37effc 100644
--- a//connect/latest/adminguide/setup-traffic-distribution-groups.md
+++ b//connect/latest/adminguide/setup-traffic-distribution-groups.md
@@ -27 +27 @@ A _traffic distribution group_ is an Connect Customer resource that enables you
-  * When you create a replica Connect Customer instance, a default traffic distribution group is created for it. The default traffic distribution group is the only traffic distribution group where you can change the `SignInConfig` distribution. See the `IsDefault` parameter in the [TrafficDistributionGroup](https://docs.aws.amazon.com/connect/latest/APIReference/API_TrafficDistributionGroup.html) data type. You use `SignInConfig` to choose which backend sign-in servers are used to facilitate the agent signing in to their Connect Customer instance. For example, if you call `UpdateTrafficDistribution` with a modified `SignInConfig` and a non-default `TrafficDistributionGroup`, an `InvalidRequestException` is returned.
+  * When you create a replica Connect Customer instance, a default traffic distribution group is created for it. The default traffic distribution group is the only traffic distribution group where you can change the `SignInConfig` distribution. See the `IsDefault` parameter in the [TrafficDistributionGroup](https://docs.aws.amazon.com/connect/latest/APIReference/API_TrafficDistributionGroup.html) data type. You use `SignInConfig` to choose which backend sign-in servers are used to help the agent signing in to their Connect Customer instance. For example, if you call `UpdateTrafficDistribution` with a modified `SignInConfig` and a non-default `TrafficDistributionGroup`, an `InvalidRequestException` is returned.