Cloud service · AWS · Updated

Amazon Application Recovery Controller (ARC) - Amazon Application Recovery Controller (ARC) coordinates application recovery across AWS Availability Zones and Regions through traffic controls, readiness checks, and recovery orchestration.

In short

ARC helps engineers prepare for infrastructure impairments and execute recovery for applications deployed across multiple Availability Zones or AWS Regions. It provides zonal shift, zonal autoshift, routing controls, readiness checks, and Region switch plans, while relying on the application architecture for redundant capacity and data replication.

Cloud Services Hub →

9 key features of Amazon Application Recovery Controller (ARC)

01
Operator-initiated zonal shift

Temporarily shift traffic for supported resources away from an impaired Availability Zone without selecting a particular destination zone. Set an expiration and verify that the remaining zones have enough capacity before extending the shift.

02
AWS-initiated zonal autoshift

Enable AWS to move traffic away from an Availability Zone when AWS detects a potential infrastructure impairment. This complements application monitoring but does not replace operator-driven recovery for application-specific failures.

03
Scheduled and on-demand practice runs

Exercise operation without one Availability Zone through zonal autoshift practice runs. Capacity-balance pre-checks for supported resource types help identify unsuitable conditions before a practice run begins.

04
Highly available routing controls

Use cluster-hosted on/off controls with Route 53 health checks to direct DNS-based failover. Prepare clients to use the cluster's Regional endpoints and retry another endpoint when necessary.

05
Routing safety rules

Apply safeguards to routing-control changes, such as preventing a configuration that turns off all application destinations. Design these rules around valid operating states and test their behavior during recovery exercises.

06
Recovery readiness checks

Continuously evaluate supported resources for configuration, capacity, and recovery-related differences. Use findings to correct standby-environment drift, while retaining separate application health checks and failover tests.

07
Multi-Region recovery plans

Define Region switch plans that orchestrate recovery actions across Regions and accounts. Execution dashboards and logs help operators follow progress and retain evidence of recovery steps.

08
Service actions and custom recovery steps

Region switch execution blocks support recovery operations such as database failover, compute scaling, Lambda invocation, and Systems Manager Run Command. Target-health waits and service quota parity checks help address dependencies that could otherwise delay recovery.

09
Event-processing and post-recovery orchestration

Use Lambda event source mapping execution blocks to coordinate event processing during Regional failover. Post-recovery workflows can organize follow-up actions after the application has switched Regions.

Where Amazon Application Recovery Controller (ARC) is used

  1. 01
    Mitigate an isolated Availability Zone impairment

    Initiate a zonal shift for supported resources when errors or latency are isolated to one zone. Monitor application health and capacity in the remaining zones while investigating the impairment.

  2. 02
    Automate infrastructure-driven zonal recovery

    Enable zonal autoshift for suitable multi-AZ workloads so AWS can initiate traffic evacuation during detected infrastructure problems. Use practice runs to validate that the application tolerates the loss of a zone.

  3. 03
    Coordinate active-passive Regional failover

    Create a Region switch plan that prepares standby capacity, performs supported database recovery actions, validates dependencies, and updates traffic routing. Measure actual execution time against the application's recovery-time objective.

  4. 04
    Guard operator-controlled traffic changes

    Use routing controls and safety rules when incident commanders need explicit control over Regional traffic placement. Prevent invalid combinations such as disabling every serving endpoint.

  5. 05
    Detect standby-environment drift

    Use readiness checks to identify supported configuration or capacity differences between recovery environments. Resolve findings during normal operations rather than discovering them during a failover.

  6. 06
    Exercise and document disaster recovery

    Run controlled Regional recovery exercises and zonal practice runs to validate permissions, capacity, sequencing, and operational procedures. Use execution records alongside application telemetry to document recovery outcomes.

How Amazon Application Recovery Controller (ARC) is priced

Routing-control cluster charges

Routing control is charged per provisioned cluster-hour, rather than only when failover occurs. Include continuously provisioned recovery clusters in the application's baseline operating cost.

Readiness-check resource charges

Readiness checks are charged according to the resources audited and the duration of auditing. The number of monitored resources affects ongoing cost even when no recovery operation is executed.

Region switch plan charges

Region switch has separate plan-based charges. Budget for configured recovery plans and the infrastructure or service operations that their executions use.

Zonal recovery without an additional ARC fee

Zonal shift and zonal autoshift have no additional ARC charge. Normal charges still apply for application resources, spare capacity, monitoring, and other services used during practice runs or recovery.

Associated AWS service usage

Route 53 health checks and DNS usage, Lambda invocations, data transfer, database capacity, and other underlying services can incur their own charges. Recovery exercises and failovers can temporarily increase infrastructure consumption.

Services Amazon Application Recovery Controller (ARC) works with

ARC typically sits above existing application infrastructure rather than replacing it. Within a Region, supported load balancers and EKS configurations use zonal shift or zonal autoshift to avoid an impaired Availability Zone. Applications still need redundant placement, adequate remaining capacity, and dependencies that remain accessible after traffic moves. CloudWatch alarms help operators assess impact and provide monitoring controls for recovery exercises.

For multi-Region applications, Route 53 health checks connect ARC routing-control states to DNS routing decisions. Region switch adds orchestration around the traffic change: a plan can coordinate supported database recovery, prepare destination capacity, invoke custom Lambda actions, and execute Systems Manager commands on managed nodes. Event-driven applications can also coordinate Lambda event source mappings during the transition.

Design the workflow around dependency order and explicit success criteria. For example, validate database availability and application target health before directing clients to the recovery Region. Provision cross-account permissions and network access beforehand, make custom actions safe to retry, and test DNS convergence and client reconnection behavior. ARC coordinates these integrations, but data replication, consistency controls, and recovery capacity remain responsibilities of the underlying architecture.

Amazon Route 53Amazon Route 53

ARC routing controls integrate with Route 53 health checks associated with DNS records. For example, an operator can disable the primary Region's routing control and enable the standby Region's control to change DNS failover behavior. Account for DNS TTLs, resolver caching, and existing client connections when measuring recovery time.

Amazon CloudWatchAmazon CloudWatch

CloudWatch alarms provide recovery signals and support monitoring controls for ARC workflows, including zonal autoshift practice runs and Region switch trigger conditions. For example, use an application error-rate alarm to stop a practice run when availability degrades. Choose thresholds that distinguish expected recovery transients from conditions requiring operator intervention.

AWS LambdaAWS Lambda

Region switch can invoke Lambda functions for custom recovery actions and coordinate Lambda event source mappings through dedicated execution blocks. For example, a custom function can validate an external dependency before traffic changes, while event source mapping actions coordinate event processing in the recovery Region. Make custom actions idempotent and grant only the permissions required for recovery.

Amazon AuroraAmazon Aurora

Region switch provides execution blocks for supported Aurora recovery and scaling operations. For example, an active-passive recovery plan can coordinate global database failover and destination database capacity preparation before redirecting application traffic. Validate replication health, recovery-point implications, and application connection handling separately.

AWS Systems ManagerAWS Systems Manager

Region switch supports Systems Manager Run Command execution blocks for commands on managed nodes. For example, a recovery step can update application configuration or restart a service on recovery instances after a database endpoint changes. Ensure nodes are managed, reachable through the required service endpoints, and authorized to execute the selected commands.

What is Amazon Application Recovery Controller (ARC)

2 min read

Amazon Application Recovery Controller (ARC) provides controls for recovering applications from Availability Zone and Regional impairments. Its capabilities address different failure scopes: zonal shift and zonal autoshift operate within a Region, while routing controls and Region switch support multi-Region recovery. Readiness checks help identify configuration and capacity differences that could interfere with failover. These capabilities can be adopted separately according to the application's recovery requirements.

Zonal shift temporarily moves traffic for a supported resource away from one Availability Zone. Traffic goes to the remaining eligible Availability Zones rather than to an operator-selected destination. Engineers can initiate a shift when application telemetry indicates an isolated zonal problem. Shifts have an expiration time, so incident procedures should include monitoring, extension when necessary, and cancellation after recovery. Resource eligibility and prerequisites vary by integration; verify the requirements for the specific load balancer, Auto Scaling group, or EKS configuration.

Zonal autoshift allows AWS to initiate a traffic shift for enabled resources when AWS detects a potential infrastructure impairment. Practice runs exercise the application's ability to operate without an Availability Zone. Scheduled and on-demand practice runs help expose insufficient capacity or application dependencies before an incident. Configure appropriate monitoring and practice-run controls, and ensure that the remaining zones can sustain expected production traffic.

Routing controls are on/off switches hosted on an ARC cluster. They connect to Amazon Route 53 health checks associated with DNS records, allowing operators or automation to change which application endpoint receives traffic. Safety rules can reject state changes that violate configured safeguards, such as disabling every recovery destination. DNS caching and existing connections affect how quickly clients move; a routing-control update does not immediately redirect every request.

Region switch orchestrates the steps required to operate an application in another Region. Plans can coordinate supported service actions and custom Lambda actions, with execution visibility and logging. Depending on the workload, a plan might scale destination compute, perform a database recovery action, wait for target health, and change traffic routing. Define action ordering, permissions, success criteria, and recovery-time objectives explicitly. Test both failover and the procedure for returning to the original Region.

Readiness checks assess supported resource configurations, capacity, and related recovery prerequisites. They are preparation signals, not substitutes for application health monitoring or end-to-end recovery tests. ARC does not independently replicate application data or guarantee a recovery point objective. Database replication, storage consistency, dependency availability, and sufficient destination capacity remain architectural responsibilities.

Prepare incident access before an outage. For routing controls, retain the cluster's Regional data-plane endpoints and implement endpoint retry behavior rather than depending on configuration discovery during recovery. Readiness and recovery-control configuration operations use the US West (Oregon) Region, while routing-control state changes use cluster endpoints. Check feature-specific Regional availability, IAM permissions, service quotas, and downstream API limits before deploying recovery automation.

AWS architecture icons are the property of Amazon Web Services. BlowStack is not affiliated with or endorsed by AWS.