AWS connect high security documentation change
Summary
Clarified agent provisioning requirements for identity provider integration
Security assessment
Highlights critical requirement to prevent UserNotOnboardedException which could compromise agent redundancy capabilities during failover scenarios
Diff
diff --git a/connect/latest/adminguide/integrate-idp.md b/connect/latest/adminguide/integrate-idp.md index 8fadeb444..6b6de9b15 100644 --- a//connect/latest/adminguide/integrate-idp.md +++ b//connect/latest/adminguide/integrate-idp.md @@ -29 +29 @@ To configure Approved Origins at the instance level, follow the steps in [Use an - * Agents must be created already in _both_ your source and replica Connect Customer instances and have the same username as the role session name from your identity provider (IdP). Otherwise, you will receive a `UserNotOnboardedException` exception and risk losing agent redundancy capabilities between your instances. + * Agents must exist in _both_ your source and replica Connect Customer instances and have the same username as the role session name from your identity provider (IdP). Otherwise, you will receive a `UserNotOnboardedException` exception and risk losing agent redundancy capabilities between your instances.