---
title: "Three business decisions that define your DR success"
description: "A disaster recovery strategy executes against targets the business defines, and three decisions made before architecture selection often determine whether teams meet them. The first is drawing the recovery boundary around a business function rather than individual applications, so shared services in other accounts fall inside scope. The second is anchoring recovery time and recovery point objectives to business consequences, with stakeholders confirming the consequence of downtime and the data that must survive. The third is accounting for the full dependency chain, because an application recovers only as fast as its slowest dependency, including services owned by other teams. In one engagement, a shared authentication platform stayed in the primary Region while applications failed over, breaking user login; redefining scope around business functions exposed the dependency and supported a successful test four months later."
---

# Three business decisions that define your DR success

[AWS](https://yomu.fyi/company/aws) · Peter Garnepudi · Nov 2, 2026

**Type:** Explainer

## Summary

A disaster recovery strategy executes against targets the business defines, and three decisions made before architecture selection often determine whether teams meet them. The first is drawing the recovery boundary around a business function rather than individual applications, so shared services in other accounts fall inside scope. The second is anchoring recovery time and recovery point objectives to business consequences, with stakeholders confirming the consequence of downtime and the data that must survive. The third is accounting for the full dependency chain, because an application recovers only as fast as its slowest dependency, including services owned by other teams. In one engagement, a shared authentication platform stayed in the primary Region while applications failed over, breaking user login; redefining scope around business functions exposed the dependency and supported a successful test four months later.

## Context

The post is Part 1 of a three-part series and builds on the AWS Resilience Lifecycle Framework and AWS Resilience Analysis Framework. It draws on a real enterprise DR engagement in which applications failed over correctly but a shared authentication platform remained in the primary Region, causing login failures. Part 2 covers progressive validation testing and Part 3 covers running a DR readiness engagement.

## Approach / What changed

Define recovery boundaries around end-to-end business functions rather than individual applications, bringing shared services in other accounts into scope. Use a business impact analysis and have business stakeholders confirm the consequence attached to each hour of downtime and the records that must survive. Document every dependency the function calls, note each dependency’s recovery target, and set the commitment against the slowest link; obtain written commitments from owning teams. Prefer recovery paths that read existing state, and pre-provision dependencies in the recovery Region where possible.

## Takeaways

- A shared authentication platform using Route 53 simple routing with no health checks or failover stayed in the primary Region during a DR exercise, so downstream applications could not authenticate users even though each application failed over correctly.
- An application with a 1-hour recovery target called a shared identity service with a 4-hour target, making its achievable RTO 4 hours regardless of its own architecture.
- Reading existing data can continue during an impairment, but creating or modifying IAM roles and Route 53 records depends on single-Region control planes, so recovery paths that must create resources mid-event carry more risk.

## FAQ

### Why did failing over every application still miss the recovery target?

The shared authentication platform was outside the recovery scope and had no health checks or failover configuration, so it stayed in the primary Region. Applications moved but users could not authenticate, so the end-to-end business function did not work.

### How should RTO and RPO be set with the business?

RTO should attach a consequence to each hour of downtime, and RPO should identify which records must survive and whether that can be proven. Business stakeholders should confirm whether asynchronous replication's in-flight data loss is acceptable or synchronous writes' latency cost is required.

### What dependency risk matters during a Regional impairment?

Reading existing data, credentials, and DNS records can keep working, but creating or modifying IAM roles and Route 53 records runs through control planes in a single Region. A recovery path that must create or change resources mid-event may not hold, so those changes should be settled ahead of time.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [AWS](https://yomu.fyi/topic/aws), [Disaster Recovery](https://yomu.fyi/topic/disaster-recovery), [Resilience](https://yomu.fyi/topic/resilience)

- Source: [AWS](https://aws.amazon.com/blogs/architecture/three-business-decisions-that-define-your-dr-success)
- Source URL: https://aws.amazon.com/blogs/architecture/three-business-decisions-that-define-your-dr-success
- Ingested by Yomu: 2026-11-02T18:01:09.357Z

[Read original post](https://aws.amazon.com/blogs/architecture/three-business-decisions-that-define-your-dr-success)
