Display
Global Resiliency
About five minutes of reading
AWS says Global Resiliency is the supported multi-Region approach, and that unsupported designs can affect quotas and the SLA story.
You replicate a linked instance, put numbers in a traffic distribution group, and shift telephony and agents in 10 percent steps. Pairs are Northern Virginia and Oregon, Frankfurt and London, Tokyo and Osaka. New instances from 1 September 2026 get global routing, analytics, and contact search by default. Older ones can be migrated on request.
ReplicateInstance copies flows, modules, users, profiles, queues, hours, quick connects, and number associations. It does not copy prompts that live only as loose S3 objects in the way people assume. Read the replica page before the test.
Number on this page: Steps 10%. Traffic distribution increments
Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.
Picture from this room.
What usually goes wrong: A second unrelated instance and a DNS trick.
Which term matches this description? The supported multi-Region design. Pairs are us-east-1 with us-west-2, eu-central-1 with eu-west-2, and ap-northeast-1 with ap-northeast-3.
The supported multi-Region design. Pairs are us-east-1 with us-west-2, eu-central-1 with eu-west-2, and ap-northeast-1 with ap-northeast-3. The term is Global Resiliency.
Set up Connect Customer Global Resiliency - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? The only Regions Global Resiliency links. Osaka is a replica Region for Tokyo, and inbound delivery there can take up to 20 seconds.
The only Regions Global Resiliency links. Osaka is a replica Region for Tokyo, and inbound delivery there can take up to 20 seconds. The term is Region pair.
Create a replica of your existing Connect Customer instance - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? The object that splits telephony and agent sign-in across the two Regions in 10 percent steps.
The object that splits telephony and agent sign-in across the two Regions in 10 percent steps. The term is Traffic distribution group.
Set up Connect Customer Global Resiliency - Amazon Connect Customer AWS docs. last checked 2026-10
Set up Connect Customer Global Resiliency - Amazon Connect Customer AWS docs. last checked 2026-10
The prose is a study paraphrase. The link is the source of the facts.
Open the Global Resiliency mind map
AWS supports one multi-Region pattern. A home-built second instance is not that pattern.
A second unrelated instance and a DNS trick.
Global Resiliency uses a traffic distribution group across a supported Region pair. Telephony percentage moves in steps of 10. A second instance you created by hand is not this resource.
Resources:
Pair:
Type: AWS::Connect::TrafficDistributionGroup
Properties:
Name: campus-pair
InstanceArn: !GetAtt SourceInstance.Arn
Description: Virginia source with an Oregon replica
Join records on ContactId. The integration map room lists the seams.
A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.
Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.