---
title: "Self-service regional failover with Amazon Application Recovery Controller Region Switch and centralized ingress controls"
description: "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."
---

# Self-service regional failover with Amazon Application Recovery Controller Region Switch and centralized ingress controls

[AWS](https://yomu.fyi/company/aws) · Greg Willson · Nov 10, 2026

**Type:** Problem & solution

## Summary

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.

## Context

Regulated enterprises with centralized ingress proxy fleets need to enable application team autonomy for disaster recovery while maintaining security controls and compliance.

## Approach / What changed

Use Amazon ARC Region Switch to create failover plans that application teams own, with Route 53 Private Hosted Zones for DNS control, Transit Gateway peering for cross-region networking, and optionally VPC Lattice for per-service testing. A central parent plan coordinates child plans across teams via AWS Resource Access Manager.

## Takeaways

- ARC Region Switch automatically evaluates plan configuration, IAM permissions, and resource readiness multiple times per hour to surface issues before failover.
- Application teams control failover by managing Route 53 Private Hosted Zone records, while centralized ingress proxy fleets remain unchanged and enforce security.
- A central parent plan can run dependent child plans in order, enabling coordinated portfolio-level failover from a single action.

## FAQ

### How does ARC Region Switch prevent configuration drift?

ARC Region Switch automatically evaluates plan configuration, IAM permissions, and resource readiness multiple times per hour, surfacing issues before they block recovery. Warnings are visible on the console and available through EventBridge or the API.

### How can teams fail over independently without touching centralized ingress?

Application teams control a Route 53 Private Hosted Zone with failover records that the ingress proxy fleet uses to resolve the active endpoint. Changing health check state shifts traffic without editing DNS records or proxy configurations, preserving security controls.

### How does portfolio-level failover work with multiple teams?

A central parent plan runs each team's child plan in dependency order, shared through AWS Resource Access Manager. A single action initiates coordinated recovery across the enterprise, with each team retaining ownership of their recovery logic.

**Tags:** [ARC Region Switch](https://yomu.fyi/topic/arc-region-switch), [AWS](https://yomu.fyi/topic/aws), [Disaster Recovery](https://yomu.fyi/topic/disaster-recovery), [Failover](https://yomu.fyi/topic/failover), [Route 53](https://yomu.fyi/topic/route-53)

- Source: [AWS](https://aws.amazon.com/blogs/architecture/self-service-regional-failover-with-amazon-application-recovery-controller-region-switch-and-centralized-ingress-controls)
- Source URL: https://aws.amazon.com/blogs/architecture/self-service-regional-failover-with-amazon-application-recovery-controller-region-switch-and-centralized-ingress-controls
- Ingested by Yomu: 2026-11-10T18:01:07.459Z

[Read original post](https://aws.amazon.com/blogs/architecture/self-service-regional-failover-with-amazon-application-recovery-controller-region-switch-and-centralized-ingress-controls)
