Independent study lab

This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.

Contact: https://cyphermonkeylabs.com/#contact

Migration patterns that survive contact with a Monday — Ecosystem

Glossary

Global Resiliency 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.
Traffic distribution group The object that splits telephony and agent sign-in across the two Regions in 10 percent steps.
Replica instance The linked instance created by ReplicateInstance. Flows, users, queues, and profiles are copied. S3 prompts are not.
Region pair The only Regions Global Resiliency links. Osaka is a replica Region for Tokyo, and inbound delivery there can take up to 20 seconds.

Mind map

Open the Global Resiliency mind map

Sister technologies

AWS supports one multi-Region pattern. A home-built second instance is not that pattern.

Config and troubleshooting

Porting the main toll-free number as the first test.

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.

TrafficDistributionGroup

CloudFormation study snippet

Resources:
  Pair:
    Type: AWS::Connect::TrafficDistributionGroup
    Properties:
      Name: campus-pair
      InstanceArn: !GetAtt SourceInstance.Arn
      Description: Virginia source with an Oregon replica

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

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.

Open the mapping room

Future hooks

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.

Sources and go deeper

The voice channel in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
Set up Connect Customer Global Resiliency - Amazon Connect Customer AWS docs. last checked 2026-10
Create a replica of your existing Connect Customer instance - Amazon Connect Customer AWS docs. last checked 2026-10
AWS History and Timeline regarding Amazon Connect - Overview, Functions, Features, Summary of Updates, and Introduction to Amazon Connect Customer | hidekazu-ko community. last checked 2026-10
Amazon Web Services - Wikipedia Wikipedia. last checked 2026-10

sources.json