---
title: "ARC Region Switch: A Layered Map of Regional Failover Ownership"
description: "ARC Region Switch is a managed failover orchestrator that runs team-owned plans in dependency order. This diagram maps its trigger, orchestration, execution, and region layers and the ownership boundary."
---

# ARC Region Switch: A Layered Map of Regional Failover Ownership

**Type:** [Architecture](https://yomu.fyi/visual-explainers/category/architecture.md)

![Layered diagram: CloudWatch alarm and manual approval feed an orchestration layer where a parent plan runs team child plans in dependency order, then execution blocks for database promotion, compute scaling, and traffic redirection; a right rail marks platform versus app-team ownership.](https://yomufyi.s3.us-east-1.amazonaws.com/visual-explainers/80c8eb75-9a7e-4019-8ada-79046bd52945/image-0d3a161e-7e8f-4d04-a03a-7c4ab546007c.webp)

> ARC Region Switch is a managed failover orchestrator that runs team-owned plans in dependency order. This diagram maps its trigger, orchestration, execution, and region layers and the ownership boundary.

## Explanation

Centralized ingress fleets keep regulated environments secure, but they also turn regional failover into a coordination problem between platform and application teams. ARC Region Switch splits that work into layers: alarms or manual approvals trigger plans, a parent plan runs each team's child plan in dependency order, and execution blocks handle database promotion, compute scaling, and traffic redirection. Ownership stays explicit, with the platform owning shared transit and ingress while teams own their DNS records and recovery logic. The diagram is a map for deciding which layer should own each failover step.

## FAQ

### When should a failover step wait for manual approval?

Region Switch plans can be triggered automatically from CloudWatch alarms or run manually with approval steps, so the choice is made per plan rather than fixed by the tool. The post frames this as the trade between fast detection and human judgment, and the same plan structure supports either path. Teams decide which steps carry enough blast radius to justify a checkpoint.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture.md), [ARC Region Switch](https://yomu.fyi/topic/arc-region-switch.md), [AWS](https://yomu.fyi/topic/aws.md), [Disaster Recovery](https://yomu.fyi/topic/disaster-recovery.md), [Failover](https://yomu.fyi/topic/failover.md), [Resilience](https://yomu.fyi/topic/resilience.md)

## Related reading

### [Using mathematics to validate network configurations](https://yomu.fyi/post/using-mathematics-to-validate-network-configurations.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Dan DaCosta
- Published: Nov 11, 2026
- Type: Explainer

Wide-area networks (WANs) require segmentation to isolate resources, but modern network size makes exhaustive packet-based mapping impractical, so organizations historically relied on incomplete sampling. AWS’s Tiros automated-reasoning tool, previously used for reachability analysis in services like Amazon Inspector and VPC Reachability Analyzer, now offers a static alternative that examines network topology without dynamic packet traffic. Tiros collects a customer’s Cloud WAN configuration from route tables, attachments, and policy documents, then converts those configurations into logical propositions. The system queries Tiros for satisfying assignments corresponding to paths and checks that no path exists between segments the policy declares should be isolated. If actual reachability matches expected segmentation the validation succeeds; otherwise it alerts an operator, and analyses can run as frequently as every hour.


### [Validating GPU Platforms with Runtime AI Inventory via the NVIDIA DSX AI Factory](https://yomu.fyi/post/validating-gpu-platforms-with-runtime-ai-inventory-via-the-nvidia-dsx.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Mark Chmarny
- Published: Nov 11, 2026
- Type: Explainer

NVIDIA AICR and Google’s k8s-aibom address two ends of AI infrastructure lifecycle validation. AICR generates version-locked recipes and reproducible deployment bundles for GPU-accelerated Kubernetes, recording desired configuration for hardware, cloud, OS, and intent. k8s-aibom watches Kubernetes workload and pod APIs to emit a CycloneDX 1.6 AIBOM for each recognized AI workload, including models, inference runtimes, agents, and RAG components. The integration is opt-in per namespace via the label aibom.k8saibom.dev/enabled=true. AIBOM attributes carry one of four confidence tiers with an evidence locator, so reviewers can see how each claim was reached.


### [Choosing QuePaxa, an unusual consensus algorithm](https://yomu.fyi/post/choosing-quepaxa-an-unusual-consensus-algorithm.md)
- Company: [Cloudflare](https://yomu.fyi/company/cloudflare.md)
- Author: James Larisch
- Published: Nov 11, 2026
- Type: Explainer

Cloudflare is building Meerkat, an experimental distributed consensus service for its global control plane, using the QuePaxa consensus algorithm. Common leader-based algorithms like Raft and Paxos degrade under volatile network conditions because they stall when the leader becomes unreachable or slow. QuePaxa is leaderless, allowing any proposer to drive decisions without a single point of failure. Proposers cooperate by using a shared data structure to track pending ballots and back off when they detect contention, preventing the destructive interference that causes metastable failures. Cloudflare is formally verifying its Rust implementation of QuePaxa and plans to share benchmarks and lessons learned in future posts.


### [Control multicluster costs with right-sizing in Red Hat Advanced Cluster Management 5](https://yomu.fyi/post/control-multicluster-costs-with-right-sizing-in-red-hat-advanced-clust.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Raj Zalavadia, Darshan Vandra
- Published: Nov 11, 2026
- Type: Announcement

Red Hat Advanced Cluster Management 5 makes the multicluster observability add-on (MCOA) delivery model and Perses dashboards generally available for namespace and OpenShift Virtualization right-sizing recommendations. The release replaces the earlier policy-based delivery path with MCOA distributing PrometheusRule resources via ManifestWork and Perses providing the primary integrated right-sizing experience in the console. It also adds configurable percentile profiles for more precise CPU and memory recommendations. Upgrades from version 2.16 or 2.17 require no migration action, and the platform automatically removes legacy resources. The new architecture aligns right-sizing with the rest of the observability stack, which already used MCOA for metrics, logging, and tracing.


### [Self-service regional failover with Amazon Application Recovery Controller Region Switch and centralized ingress controls](https://yomu.fyi/post/self-service-regional-failover-with-amazon-application-recovery-contro.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Greg Willson
- Published: Nov 10, 2026
- Type: Problem & solution

Centralized ingress proxy fleets enforce security in regulated industries but create coordination overhead that conflicts with application team autonomy for disaster recovery failover. Amazon Application Recovery Controller (ARC) Region Switch, launched in August 2025, provides a fully managed failover orchestrator that addresses configuration drift, slow detection, and recovery logic drift through automatic plan evaluation and codified workflows. The solution uses centrally managed AWS Transit Gateways with application-team-owned Route 53 Private Hosted Zones, establishing clear boundaries where teams control DNS records without needing to coordinate with infrastructure teams. Application teams create Region Switch plans with execution blocks for database promotion, compute scaling, and traffic redirection, and can trigger them automatically from CloudWatch alarms or manually with approval steps. A central parent plan can run each team’s child plan in dependency order, enabling coordinated portfolio-level failover while preserving team ownership of recovery logic and maintaining security posture.
