Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
Tips for avoiding issues when shifting agents in your Amazon Connect instance across Regions - Amazon Connect

Tips for avoiding issues when shifting agents in your Amazon Connect instance across Regions

PDFRSS

  • Whenever you update the traffic distribution for agents be sure to also update the traffic distribution for inbound voice contacts. Otherwise, you might end up in a situation where one Region is heavy on agents while the other is heavy on telephony traffic.

  • Before associating users to a traffic distribution group, make sure the same username exists in both the source and replica Amazon Connect instances. Otherwise, when you associate a user to a traffic distribution group but the user with the username does not exist in the replica Region, you will get an InvalidRequestException error.

  • You must call the AssociateTrafficDistributionGroupUser API to associate agents to a traffic distribution group in the source Region. If you attempt to do this while in the replica Region, you will get a ResourceNotFoundException error.

Previous topic:

Set up Agent Workspace

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.