Cloud concept · Updated

Warm Standby - Warm standby is a disaster recovery strategy that keeps a scaled-down, functional copy of a production environment running in a separate recovery location.

In short

The recovery environment maintains current application components and replicated data, but normally has less capacity than the primary environment. During a disaster, engineers promote data stores where necessary, increase capacity, and redirect traffic, balancing recovery speed against the cost of keeping duplicate infrastructure running.

Cloud Concepts Hub →

6 key aspects of Warm Standby

Warm standby combines a running secondary environment, replicated data, and tested scaling and failover procedures to balance recovery speed with ongoing cost.

01
Running, reduced-capacity environment

Keep all essential application tiers operational in the recovery location, rather than deploying them only after a disaster. Size the standby to support validation and limited operation, with a tested path to production capacity.

02
Data replication with explicit RPO

Replicate databases and other persistent state according to the workload's acceptable data-loss window. Monitor replication lag and understand which acknowledged writes could be lost during an unplanned failover.

03
Measured recovery time

Include detection, authorization, promotion, scaling, validation, and traffic switching when measuring RTO. Test the complete recovery procedure rather than treating resource startup time as the recovery time.

04
Controlled failover and failback

Use a runbook or tested automation to establish the recovery location as authoritative and avoid conflicting writers. Plan how to synchronize data and return traffic after the original location becomes usable.

05
Configuration and dependency readiness

Keep application versions, infrastructure definitions, permissions, and regional dependencies aligned. Verify that recovery does not require access to services or artifacts available only in the failed location.

06
Cost and readiness balance

Accept ongoing standby and replication costs to reduce the work required during an outage. Retain independent backups because a replicated environment may also receive destructive or corrupting changes.

Cloud services for Warm Standby

EC2 and EC2 Auto Scaling provide a running application fleet that can expand during recovery. RDS replication maintains a secondary database where supported, while S3 replication copies required objects. CloudFormation helps keep both environments structurally consistent, with regional configuration and capacity differences managed explicitly. Route 53 redirects clients once the recovery environment is ready. These services do not constitute an automatic recovery guarantee: the runbook must coordinate database promotion, scaling, dependency checks, and traffic changes. Regular exercises should measure replication lag, application readiness, recovery time, and the ability to fail back safely.

Amazon EC2Amazon EC2

EC2 instances can host a reduced-capacity application environment in a recovery Region. Keep the required application tiers running and validate instance launch dependencies and capacity availability before relying on expansion during an incident.

Amazon RDSAmazon RDS

For supported engines and configurations, cross-Region read replicas can maintain a database copy for recovery. Promotion and application connection changes must be included in the failover procedure; asynchronous replication means recent writes may be lost.

Amazon Route 53Amazon Route 53

DNS failover routing and health checks can direct clients toward a recovery endpoint. Coordinate routing with database promotion and application readiness, and account for DNS caching rather than assuming every client switches immediately.

Amazon EC2 Auto ScalingAmazon EC2 Auto Scaling

Auto Scaling groups can maintain a small running fleet and increase desired capacity during recovery. Scaling requires suitable quotas, launch configuration, available capacity, and enough time for instances to become healthy.

Amazon S3Amazon S3

S3 Cross-Region Replication can copy application objects to a recovery Region, with replication rules and lag affecting recovery readiness. Destination permissions, encryption access, and application bucket references must also be prepared.

AWS CloudFormationAWS CloudFormation

CloudFormation templates can define consistent infrastructure for primary and recovery environments while allowing different capacity settings. Deploy and maintain the standby in advance; a template alone is not a running warm standby.

Warm Standby exam questions

Real practice exam questions on Warm Standby, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SOA-C03

A company runs a claims-processing application on Amazon EC2 instances in a primary AWS Region. A second Region contains an idle, full-capacity copy of the application, including web, API, and background-processing tiers, with continuously replicated data. The recovery deployment costs almost as much as production.

A CloudOps engineer must reduce the recovery Region's compute costs. Company policy requires an end-to-end synthetic claim to complete in the recovery Region every 5 minutes without starting or deploying missing application tiers. The recovery Region must not serve customer requests during normal operations. During a disaster, increasing existing application capacity is permitted before customer traffic is redirected. Tests confirm that a small instance fleet in each tier can process the synthetic claims and can scale to production capacity within the recovery time objective.

Which change should the engineer implement?

Show answerCORRECT ANSWER

Keep a reduced number of instances running in every application tier, retain continuous data replication, and configure the recovery fleet to scale to production capacity during failover.

This maintains a complete, working application at reduced capacity while lowering compute costs. Synthetic claims can exercise every tier without additional deployment or startup. During recovery, the engineer can promote replicated data stores as necessary, scale the running fleet, validate readiness, and redirect traffic. This implements warm standby.

SAP-C03

A logistics company runs a shipment-processing application on Amazon EC2 instances with an Amazon Aurora PostgreSQL database in one AWS Region. During a Regional outage, the company must restore priority shipment processing within 8 minutes and restore all processing within 40 minutes. Priority processing requires 20% of the application's normal peak compute capacity. The recovery point objective (RPO) is 1 minute.

An Aurora Global Database secondary cluster in a recovery Region consistently maintains replication lag below 10 seconds during peak-load tests. Recovery exercises establish the following timings:
• Incident detection, recovery authorization, database promotion, traffic redirection, and transaction validation take a combined 6 minutes when sufficient application capacity is already running.
• Starting the application from stopped instances or newly launched instances requires at least 18 minutes because of mandatory initialization.
• Expanding an already running application fleet from 20% to 100% of normal peak capacity takes 25 additional minutes, including initialization and validation.

All application dependencies are available independently in the recovery Region. The company wants the LOWEST ongoing recovery infrastructure cost while meeting both service-restoration deadlines.

Which architecture should a solutions architect recommend?

Show answerCORRECT ANSWER

Maintain the Aurora secondary cluster and a running, fully configured application deployment sized for 20% of normal peak capacity. Keep releases and configuration synchronized. During recovery, promote the database, direct priority processing to the running fleet, and expand the fleet to full capacity.

This warm standby deployment has enough application capacity already running to restore priority processing in the tested 6 minutes, meeting the 8-minute deadline. Expanding capacity takes another 25 minutes, restoring all processing within 31 minutes and meeting the 40-minute deadline. The measured database replication lag supports the 1-minute RPO. Keeping only the capacity needed for initial recovery running costs less than maintaining a full-sized duplicate.

SAA-C03

A company runs an order-processing application in a primary AWS Region. A second Region contains a running application fleet at reduced capacity and an Amazon RDS for MySQL cross-Region read replica. The replica uses asynchronous replication. The application fleets connect to their respective regional database endpoints. Amazon Route 53 currently directs all customer traffic to the primary Region.

The company is automating recovery from a complete primary Region outage. Recovery must use the data already replicated to the second Region without provisioning a new database. Before customer traffic is redirected, the recovery application must be able to process writes and handle the full production load. The company accepts the possible loss of transactions that have not yet replicated.

Which recovery workflow meets these requirements?

Show answerCORRECT ANSWER

Promote the cross-Region read replica to a standalone database, scale the recovery application fleet to production capacity, verify that the recovery application can complete writes, and then redirect customer traffic through Route 53.

Promotion makes the existing read replica an independent, writable database without provisioning a replacement database. Scaling and validating the application before redirecting traffic ensure that the recovery deployment can assume the primary deployment's responsibilities. Asynchronous replication can leave some recent transactions unavailable, which the company accepts.

Practice Warm Standby in a full exam

Questions on Warm Standby in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Warm Standby

2 min read

Warm standby keeps a complete, working version of a workload running at reduced capacity in a separate recovery location, often another cloud Region. The standby includes the application tiers, networking, data stores, and supporting dependencies needed to provide service. Unlike an environment assembled only after an outage, it can already process requests at a limited scale, although it does not normally serve production traffic.

The defining distinction is functional readiness rather than full production capacity. A pilot light typically keeps essential components, particularly data replication, running while other application infrastructure must be started or deployed during recovery. Warm standby has the application environment running already; recovery focuses on promoting writable data stores, scaling resources, validating readiness, and shifting traffic. Backup and restore generally requires more reconstruction, while active-active runs multiple locations that normally serve production traffic. These strategies offer different cost, complexity, and recovery characteristics rather than interchangeable labels.

Recovery objectives should determine the design. Recovery time objective, or RTO, is the maximum acceptable time to restore service after disruption. For warm standby, this includes incident detection, the decision to fail over, database promotion, capacity expansion, and traffic redirection. Recovery point objective, or RPO, is the maximum acceptable amount of data loss expressed as time. Asynchronous replication can leave recent writes unavailable in the recovery location, so a running standby does not imply zero data loss. Neither RTO nor RPO is guaranteed by choosing the strategy; both require measurement through realistic exercises.

For example, an online ordering application might run its primary environment in one Region and a smaller application fleet with a replicated database in another. The standby receives application updates and configuration changes alongside production. After a primary-region failure, operators assess replication lag, prevent conflicting writes where possible, promote the recovery database, scale the application fleet, test critical transactions, and redirect clients. If the design permits limited service before scaling completes, recovery can be staged, but restoring full production capacity remains part of the recovery plan.

Capacity and dependencies are common sources of failure. A configured scaling policy does not guarantee that instances will be available during a regional incident. Teams should check service quotas, instance availability, database scaling constraints, startup times, and any need for capacity reservations. Recovery also depends on certificates, secrets, encryption keys, identity permissions, container images, external integrations, and connectivity being available independently of the failed location. DNS failover can help redirect clients, but caching and existing connections can delay the transition.

Warm standby costs more than backup and restore or a minimal pilot light because application resources and data replication run continuously. It usually costs less than maintaining multiple fully provisioned production environments. Replication does not replace backups: accidental deletion, corruption, or malicious changes may propagate to the standby. Maintain protected recovery points, rehearse failover under representative load, and document failback, including data synchronization and controlled traffic movement. High availability across Availability Zones can complement this strategy, but does not by itself provide recovery from a regional outage.

Learn Warm Standby in lessons

7 short lessons on Warm Standby in 3 certification courses.

and 1 more lesson

Open the lessons