Amazon Connect · ACGR

If one AWS Region has trouble, your customers still get through.

We run your contact center in two AWS Regions with Amazon Connect Global Resiliency: the same phone numbers, flows, queues and agents, plus the integrations around them, with a tested failover that moves calls within minutes.

2
AWS Regions, live for an airline and a healthcare company
<15 min
recovery target for the airline
≤5 min
of data at risk, at most
0
phone number changes for customers during a failover

Figures from our airline and healthcare migrations. Read the airline case study

01For you
Before and after · One site to two Regions

From one point of failure to two Regions.

The same bad day, two ways: a single-site contact center on the left, Amazon Connect with Global Resiliency on the right.

Simulated day09:50
Before · One site
All systems normal
0customers couldn’t get through
Customers hear: ringing, then an agent
After · Amazon Connect in two AWS Regions (ACGR)
All systems normal
Traffic distribution group · same phone numbers
US East 100%
0customers couldn’t get through
Before and after
BeforeAfter
Customers who couldn’t get through––
Time down––
Phone numbers––
Agents––
Getting back to normal––
  • Amazon Connect runs in two AWS Regions, with your instance replicated to the second one.
  • Phone numbers belong to a traffic distribution group, so calls move without customers dialing anything new.
  • Traffic moves all at once or in steps, and moves back the same way once the Region is healthy.

Simulation. The outage, the times and the counts (10 calls a minute) are illustrative.

02For you

What we build for resiliency

Three stages: a backup Region that is always ready, a tested move when something goes wrong, and drills so it works on the day.

01

Set up the backup Region

  • A backup copy of your contact center

    One Region. If it has trouble, so do your phones.A second, ready contact center in another Region

    Global Resiliency replica instance
  • Keep your phone numbers in a failover

    Numbers tied to one Region.The same numbers, served from either Region

    Traffic distribution groups
  • CRM, data and WFM in both Regions

    Calls fail over, the CRM lookup does not.Integrations ready in the second Region

    Lambda, data and integrations in both Regions
02

When a Region has a problem

  • Move all calls to the backup in minutes

    A bridge call at 2 am, deciding what to do.A tested, one-step move

    Traffic distribution update · failover pipeline
  • Agents switch Regions with the calls

    Agents signed in where there are no calls.Same agents, same desktop, other Region

    Agent distribution across Regions
  • Return to normal a little at a time

    Flip everything back and hope it holds.Back to normal, 10% at a time

    Distribution by percentage
03

Test it before you need it

  • Regular failover drills

    A disaster plan nobody has run.Rehearsed, with recovery time measured

    Scheduled failover tests
  • Agreed recovery times

    “As fast as we can.”Targets agreed up front, like under 15 minutes

    Recovery targets per line of business

Feature names from the AWS Amazon Connect Global Resiliency guide.

03For you
Global routing · both Regions active

Any call, any agent, in either Region.

Move the sliders to split calls and agents between Regions, in 10% steps like the real controls. With global routing on, a call that arrives in one Region can be answered by a free agent in the other.

US East (N. Virginia)us-east-1 · source
Calls arriving50%
Waiting0
US West (Oregon)us-west-2 · replica
Calls arriving50%
Waiting0
Agent on a call from their own RegionAgent on a call from the other RegionFree agent

Both Regions are active. With global routing on, each call goes to the best free agent in either Region.

What can be routed across Regions today
  • ✓Voice calls
  • ✓Callbacks, queued and customer-first
  • ✓Chats and tasks
  • ✓Emails
  • ✓Supervisor monitoring and barge
  • ✓Routing to a specific agent
  • –In-app, web and video calling (same Region only)
  • –Screen recordings (same-Region contacts only)

Illustrative model with 20 agents. Global routing is on by default for Global Resiliency instances created from September 1, 2026, and can be paused without dropping live calls. Source: AWS, Global routing across ACGR Regions.

04For you
Our Global Resiliency services

Global Resiliency services, from setup to failover.

Add a second Region to the Amazon Connect you already run, turn on global routing so both Regions work every day, and use our tool to fail over and back in minutes.

Service

Implement Global Resiliency on your existing Amazon Connect

We add a second AWS Region to the Amazon Connect you already run. We set up the replica, move your numbers onto traffic distribution groups, deploy everything around it to both Regions, and prove the failover before you rely on it.

Ideal for: Contact centers running Amazon Connect in one Region that need a second.

What’s included
  • Readiness check
  • Replica instance
  • Numbers and traffic groups
  • Everything around it
  • Proven failover

Outcome: A second Region that can take every call, tested and documented.

How we deliver it
  1. Readiness check. Supported Region pair, AWS Enterprise Support or Unified Operations, SAML sign-in and service quotas matched in both Regions.
  2. Replica instance. A linked copy of your instance in the second Region, with flows, queues, routing profiles and users kept in step.
  3. Numbers and traffic groups. Numbers ported to Amazon Connect and claimed to traffic distribution groups, one line of business at a time.
  4. Everything around it. Lambda with the same names in both Regions, flows using the Region they run in, and bots copied with Amazon Lex Global Resiliency.
  5. Proven failover. A planned failover and failback, measured against your recovery targets, before you rely on it.
Service

Enable global routing on your existing setup

We turn on global routing for your Global Resiliency setup, so both Regions take calls every day. We update your desktops, integrations and pipelines first, then switch it on with your AWS team and validate it.

Ideal for: Global Resiliency customers who want both Regions taking calls every day.

What’s included
  • Impact review
  • New instance addresses
  • Integrations updated
  • Switch it on
  • Validate

Outcome: Both Regions active every day, so the backup is always proven.

How we deliver it
  1. Impact review. Desktops, CRM, WFM, reporting and event pipelines checked for what changes when calls cross Regions.
  2. New instance addresses. Region-based instance addresses added to firewalls, and custom agent desktops given both Regions’ addresses.
  3. Integrations updated. Contact records and agent events read from both Regions; updates to a contact sent to the Region it started in.
  4. Switch it on. Global routing enabled with your AWS team, then agents sign in again so they can take calls from either Region.
  5. Validate. Test calls, chats and callbacks answered across Regions, with consolidated reports checked.
Service

Our failover tool: fast failover and failback

We provide and run our failover console for your contact center. Your on-call team moves calls, agents and applications between Regions in one click, or a step at a time, with a test call to prove it.

Ideal for: On-call teams that need a safe, quick way to move traffic without the console.

What’s included
  • Route all here
  • Fine control
  • Safe by design
  • Proof every time
  • Failback in steps

Outcome: Failover and failback in minutes, by the people on call.

How we deliver it
  1. Route all here. One click moves every traffic distribution group and every Global Accelerator to a Region.
  2. Fine control. Move one group or one application at a time, all at once or in 10% steps.
  3. Safe by design. Role-based access, a required remark for every change, and a full audit trail.
  4. Proof every time. A test call placed automatically after each switch, and scheduled drills that report recovery time.
  5. Failback in steps. Move back a share at a time, with checks before each step.

Global Resiliency is available for the us-east-1 and us-west-2, eu-west-2 and eu-central-1, and ap-northeast-1 and ap-northeast-3 Region pairs, and AWS enables it for your account. Steps follow the AWS Global Resiliency and global routing guides.

Talk to us about these services
05For you
Applications on Amazon Connect · one console

Switch your applications too, from one place.

Your agent desktop, CRM, APIs, data and other AWS applications follow the contact center to the other Region. One click in our failover console moves every traffic distribution group and every Global Accelerator, then proves it with a test call.

Application/Amazon Connect accounts/connect-prod-cxOCOn-call lead
connect-prod-cxActive4c1e9a07-demo-instance
Failover guideRefresh
06TDG groups02Global Accelerators148Active calls212Online agents
Region configuration
PrimaryActive
us-east-1US East (N. Virginia)
0Active calls0Online agents0In queue
SecondaryInactive
us-west-2US West (Oregon)
0Active calls0Online agents0In queue

Traffic distribution (TDG): routes phone calls and agent sessions between Regions, per Amazon Connect instance.

Global Accelerator (GA): routes application and API traffic between Regions, per AWS account.

“Route all here” moves TDGs and GAs together. To move one on its own, use Configure on its card.
Default-TDGconnect-prod-cx.my.connect.aws
12 numbers
Telephony traffic
us-east-1100%
us-west-20%
Agent traffic
us-east-1100%
us-west-20%
Sign-in distributionAgents sign in through the global endpoint, split like agent trafficNo changes today
CustomerService-TDGconnect-prod-cx.my.connect.aws
64 numbers
Telephony traffic
us-east-1100%
us-west-20%
Agent traffic
us-east-1100%
us-west-20%
Sign-in distributionSign-in setup is only available in the default TDGNo changes today
Reservations-TDGconnect-prod-cx.my.connect.aws
42 numbers
Telephony traffic
us-east-1100%
us-west-20%
Agent traffic
us-east-1100%
us-west-20%
Sign-in distributionSign-in setup is only available in the default TDGNo changes today
Loyalty-TDGconnect-prod-cx.my.connect.aws
18 numbers
Telephony traffic
us-east-1100%
us-west-20%
Agent traffic
us-east-1100%
us-west-20%
Sign-in distributionSign-in setup is only available in the default TDGNo changes today
Outbound-TDGconnect-prod-cx.my.connect.aws
8 numbers
Telephony traffic
us-east-1100%
us-west-20%
Agent traffic
us-east-1100%
us-west-20%
Sign-in distributionSign-in setup is only available in the default TDGNo changes today
HelpDesk-TDGconnect-prod-cx.my.connect.aws
6 numbers
Telephony traffic
us-east-10%
us-west-2100%
Agent traffic
us-east-10%
us-west-2100%
Sign-in distributionSign-in setup is only available in the default TDGNo changes today
Last test callPlaced automatically every morning
● Verified
Region called
us-east-1
Placed at
08:02:14
How each application follows a Region change
Agent desktopAgents sign in once through the global sign-in; the desktop follows the agent’s Region.
CRM and screen popsThe Salesforce CTI Adapter supports cross-Region calls from v5.33. Other CRMs call each contact’s own Region.
Your APIs and LambdaGlobal Accelerator sends API traffic to the active Region. Updates to a contact go to the Region where it started.
Data and reportingContact records and agent events stay in their Region, so data pipelines run in both.
WFM and quality toolsFed from both Regions, so schedules and adherence stay right after a switch.
Your other apps on AWSPortals and services behind Global Accelerator switch in the same click.

A working replica of our failover console; account names, IDs and numbers are fictional. It changes traffic distribution groups through the Global Resiliency APIs and AWS Global Accelerator traffic dials for your applications, with role-based access, required remarks, scheduled events and a full audit trail.

06For you

How we deliver resiliency

Designed around what must keep working, built as code, and proven with a real failover before go-live.

How Digiclarity deliversYour Global Resiliency, from first workshop to weekly tuning
A pod of 5 specialists
Delivery managerOwns the plan, the recovery targets and the go-live
Amazon Connect expertDesigns the replica, traffic distribution and numbers
Integration developerDeploys Lambda, data and integrations to both Regions
Amazon Connect QARuns failover and failback tests, and measures recovery
Messaging compliance specialistChecks data residency and security in both Regions
Step 1 · Plan

Agree what must keep working

We list every line of business, number and integration, and agree recovery targets for each: how fast, and how much data can be at risk.

You get
  • Dependency map
  • Recovery targets per workload
We need from you
  • Business owners for each line of business
Must be true before the next step✓ Targets signed off
For you
Why Digiclarity

A partner AWS has validated, on exactly this kind of work.

AWS partner credentials
  • AWS Advanced Tier Services PartnerRecognized by AWS for proven delivery, certified people and customer outcomes.
  • AWS Migration Services CompetencyValidated by AWS for moving and modernizing workloads on AWS at scale.
  • Amazon Connect Delivery PartnerValidated by AWS to deliver Amazon Connect, including migrations from Avaya, Genesys, Cisco and other platforms.
  • AWS AI Services CompetencyValidated by AWS for building AI into real products, including the contact center.
  • AWS Experience-Based Acceleration (EBA) partnerWe run EBA engagements with AWS to speed up migrations with hands-on, time-boxed sprints.
Security and compliance
  • ISO/IEC 27001 certifiedOur information security management system is independently certified to the international standard.
  • SOC 2 Type IIIndependent auditors have tested our security controls over time, not just at a single point.
09For you

Questions we hear first

Do customers have to call a different number?

No. Your numbers are claimed to a traffic distribution group, so the same numbers are served from whichever Region is active.

What about our CRM lookups, WFM and reporting?

Global Resiliency covers Amazon Connect. We deploy the Lambda functions, data and integrations around it to both Regions too, so a failover does not leave them behind.

How fast is a failover?

We agree recovery targets with you up front. For an airline the target was under 15 minutes, with no more than 5 minutes of data at risk, and we test against it.

Do we need anything from AWS?

Global Resiliency is enabled for your account by AWS and is available for supported Region pairs. We handle the request with your AWS team as part of the project.

Can one tool switch everything at once?

Yes. We build a failover console with one “Route all here” button. It moves every traffic distribution group (calls and agents) and every AWS Global Accelerator (application and API traffic) to the chosen Region, then places a test call to prove it worked. Access is by role, with an audit trail.

Can we test it without affecting customers?

Yes. We run planned failovers in a quiet window, and fail back in steps, a share of traffic at a time.

Start here

Plan your second Region.

Tell us what you run today and what downtime would cost you. We will come back with a resiliency outline.

  • AWS Advanced Tier Services Partner
  • AWS Migration Services Competency
  • Amazon Connect Delivery Partner
  • AWS AI Services Competency
  • AWS Experience-Based Acceleration (EBA) partner
  • ISO/IEC 27001 certified
  • SOC 2 Type II
Certified supplierMWDBE certifiedTexas HUB certifiedNCTRCA certified
+1 (214) 550-14936275 West Plano Parkway, Suite 500, Plano, Texas 75093