Study guide
10.1 Disaster Recovery, Cross-Region Replication & Backup Strategies
AWS Certified Data Engineer - Associate DEA-C01
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Streaming Data Ingestion
1.1 Kinesis Data Streams vs. Firehose Architecture & Partitioning 1.2 Amazon MSK (Managed Streaming for Apache Kafka) & Serverless Patterns 1.3 Event-Driven Streaming Ingestion with DynamoDB Streams & Lambda 1.4 Streaming Distribution, Replay & Processing State
2 Chapter 2: Batch Data Ingestion & Migration
2.1 AWS DMS (Database Migration Service) & Change Data Capture (CDC) 2.2 S3 Batch Operations & High-Throughput Bulk Data Ingestion 2.3 Hybrid Data Transfer with Snow Family & AWS DataSync 2.4 Application, API & Managed File Ingestion
3 Chapter 3: ETL Transformation with AWS Glue
3.1 AWS Glue Jobs, DynamicFrames & PySpark Transformations 3.2 Glue Crawlers, Data Catalog & Schema Evolution 3.3 Data Preparation & Quality Rules with AWS Glue DataBrew & Data Quality 3.4 Incremental Processing with AWS Glue Job Bookmarks & Partition Processing 3.5 Technical and Business Catalogs, Connections & Lineage
4 Chapter 4: Big Data Processing & Workflow Orchestration
4.1 Amazon EMR Cluster Architecture, Spark & Hadoop Ecosystem 4.2 EMR Serverless & Instance Selection (On-Demand vs. Spot Optimization) 4.3 Serverless Orchestration with AWS Step Functions 4.4 Airflow Pipeline Orchestration with Amazon MWAA 4.5 Containers, Lambda & Distributed Processing Performance 4.6 Data Engineering Code, IaC & CI/CD
5 Chapter 5: Object Storage & Data Lake Architecture
5.1 Amazon S3 Storage Classes, Lifecycle Policies & Cost Optimization 5.2 S3 Data Lake Partitioning, Bucketing & Layout Strategies 5.3 Efficient Columnar Formats: Parquet, ORC, and Avro Schema Design 5.4 S3 Performance Optimization, Multipart Uploads & Transfer Acceleration 5.5 Apache Iceberg, S3 Tables & Open Table Operations
6 Chapter 6: Data Warehousing with Amazon Redshift
6.1 Amazon Redshift Architecture, RA3 Nodes & Managed Storage 6.2 Redshift Data Modeling: Distribution Styles (KEY, EVEN, ALL) & Sort Keys 6.3 Loading & Unloading Data with COPY/UNLOAD & Redshift Spectrum
7 Chapter 7: NoSQL, Relational & Specialty Data Stores
7.1 Amazon DynamoDB Partition Keys, Global Secondary Indexes & Data Modeling 7.2 Amazon RDS & Aurora Operations, Read Replicas & Multi-AZ 7.3 Graph & Analytical Querying with Amazon Neptune, OpenSearch & Athena 7.4 Vector Stores, Indexes & LLM Data Processing
8 Chapter 8: Pipeline Operations, Monitoring & Observability
8.1 Monitoring Pipeline Health with Amazon CloudWatch Metrics & Logs 8.2 Event-Driven Alerting & Automation with EventBridge & CloudWatch Alarms 8.3 Centralized Audit Logging with AWS CloudTrail
9 Chapter 9: Troubleshooting, Data Quality & Performance Tuning
9.1 Diagnosing & Resolving AWS Glue, EMR & Lambda Execution Failures 9.2 Redshift & Athena Query Performance Tuning & Memory Management 9.3 Implementing Data Quality Frameworks & Automated Validation Checks 9.4 Visualization, Notebooks, SQL Analytics, Sampling & Skew
10 Chapter 10: High Availability, Backup & Cost Optimization
10.1 Disaster Recovery, Cross-Region Replication & Backup Strategies 10.2 Designing High Availability Architectures Across AWS Data Services 10.3 Cost Optimization & Resource Utilization across Analytics Workloads
11 Chapter 11: Data Security, Encryption & Identity Management
11.1 Fine-Grained Access Control with AWS IAM Policies, Roles & Conditions 11.2 Data Encryption at Rest & in Transit with AWS KMS & S3 Bucket Policies 11.3 Secure Credentials & Secrets Management with AWS Secrets Manager & Parameter Store 11.4 Private Network Connectivity & Isolation with AWS PrivateLink & VPC Endpoints
12 Chapter 12: Data Governance, Privacy & Compliance
12.1 Centralized Data Lake Governance & Access Control with AWS Lake Formation 12.2 Automated Sensitive Data Discovery & PII Protection with Amazon Macie 12.3 Configuration Auditing & Compliance Enforcement with AWS Config 12.4 Data Privacy, Sovereignty, Sharing & Retention Guardrails 12.5 SageMaker Unified Studio Domains, Projects & Catalog Governance
10.1 Disaster Recovery, Cross-Region Replication & Backup Strategies
Key Takeaways Explain This Topic AI
RPO (Recovery Point Objective) measures allowable data loss in time, while RTO (Recovery Time Objective) measures allowable application downtime during a disaster event.
AWS Backup provides centralized, policy-driven backup management across AWS data services including S3, DynamoDB, RDS, Aurora, EBS, EFS, and Redshift, supporting cross-Region and cross-account copy operations with KMS encryption.
Amazon S3 Cross-Region Replication (CRR) requires Bucket Versioning on both source and destination buckets, with optional S3 Replication Time Control (S3 RTC) offering a 99.9% SLA for object replication within 15 minutes.
Aurora Global Database uses storage-based asynchronous cross-Region replication, commonly with sub-second lag, and supports up to 10 secondary Regions subject to engine and Region support; measure lag instead of assuming a fixed RPO.
Disaster recovery strategies range across four main tiers: Backup & Restore (hours RPO/RTO), Pilot Light (minutes RPO/tens of minutes RTO), Warm Standby (seconds RPO/minutes RTO), and Multi-Site Active-Active (near-zero RPO/RTO).
Last updated: August 2026
10.1 Disaster Recovery, Cross-Region Replication & Backup Strategies
Designing resilient data platforms on AWS requires a rigorous understanding of disaster recovery (DR) objectives, automated backup capabilities, and cross-Region data replication patterns. In enterprise data engineering, a regional service disruption or catastrophic failure must not lead to unrecoverable data loss or prolonged platform downtime. AWS provides both centralized management services and native database/storage replication mechanisms to satisfy strict business continuity requirements.
1. Core Disaster Recovery Metrics: RPO and RTO
Every disaster recovery strategy is defined by two fundamental business requirements:
Recovery Point Objective (RPO): The maximum acceptable amount of data loss measured in time. An RPO of 5 minutes means the platform must be able to recover data up to 5 minutes prior to the failure event.
Recovery Time Objective (RTO): The maximum acceptable duration of infrastructure downtime before business operations are restored. An RTO of 1 hour means service availability must be recovered within 60 minutes of disaster declaration.
The Four Standard AWS DR Architecture Patterns
AWS categorizes DR strategies into four primary architectural patterns, offering trade-offs between cost, operational complexity, and RPO/RTO objectives. The values below are planning illustrations, not AWS service guarantees; derive tested objectives from the workload and chosen services:
DR Strategy Target RPO Target RTO Relative Cost Architectural Mechanism
Backup & Restore Hours to 24 Hours 24 Hours+ Lowest ( $ ) Daily/hourly snapshots copied to secondary Region; infrastructure created on-demand via IaC.
Pilot Light Minutes Tens of Minutes Low ( $$ ) Core data synchronously/asynchronously replicated; compute instances maintained in idle state (AMIs/templates ready).
Warm Standby Seconds Minutes Medium ( $$$ ) Scale-down version of full stack running continuously in secondary Region; scaled up during failover.
Multi-Site Active-Active Near-Zero Real-Time / Near-Zero Highest ( $$$$ ) Fully operational parallel deployments in two or more Regions with active-active traffic routing.
2. Centralized Data Protection with AWS Backup
AWS Backup is a fully managed, policy-based backup service that centralizes and automates data protection across AWS services. Rather than writing custom scripts for EBS snapshots, RDS backups, or S3 replication, engineers configure unified backup policies called Backup Plans .
Core Capabilities for Data Engineers
Supported Native Services: S3, DynamoDB, RDS, Aurora, Redshift, EBS, EFS, AWS Storage Gateway, and other services listed in the current AWS Backup feature matrix. Verify service and feature support by Region before designing a plan.
Cross-Account and Cross-Region Copies: Backup Plans can automatically copy backup snapshots to a secondary AWS Region and a separate, isolated target AWS Account (managed within AWS Organizations). This protects backups against compromised primary account credentials or regional disasters.
AWS Backup Vault Lock: Implements Write-Once-Read-Many (WORM) immutability on backup vaults. Once Vault Lock is enabled in compliance mode, even the AWS account root user cannot delete or alter backups before the retention period expires, meeting strict SEC 17a-4 and FINRA compliance rules.
Transition to Cold Storage: Backups for supported services (such as EFS or DynamoDB) can automatically transition from warm storage to cost-effective cold storage after a configurable number of days. {
- "BackupPlanName": "EnterpriseDataPlatformDRPlan",
- "Rules": [
- {
- "RuleName": "DailyCrossRegionBackup",
- "TargetBackupVault": "PrimaryVault",
- "ScheduleExpression": "cron(0 1 * * ? *)",
- "StartWindowMinutes": 60,
- "CompletionWindowMinutes": 180,
- "Lifecycle": {
- "MoveToColdStorageAfterDays": 30,
- "DeleteAfterDays": 365
- },
- "CopyActions": [
- {
- "DestinationBackupVaultArn": "arn:aws:backup:us-west-2:111122223333:backup-vault:DRVault",
- "Lifecycle": {
- "DeleteAfterDays": 365
- }
- }
- ]
- }
- ]
- }
- 3. Amazon S3 Cross-Region Replication (CRR)
For object data stored in Amazon S3, Cross-Region Replication (CRR) provides automatic, asynchronous copying of objects across S3 buckets in different AWS Regions.
Prerequisites and Technical Requirements
Versioning: S3 Versioning must be enabled on both the source and destination buckets.
IAM Permissions: The S3 service must be granted an IAM role allowing s3:GetObjectVersionForReplication on the source and s3:ReplicateObject on the destination.
KMS Key Ownership: If objects are encrypted with SSE-KMS, the replication configuration must explicitly enable KMS object replication and supply destination KMS key ARNs.
Advanced CRR Features for Analytics
S3 Replication Time Control (S3 RTC): An enterprise SLA feature that guarantees 99.9% of new objects are replicated to the target Region within 15 minutes . It includes detailed Amazon CloudWatch metrics ( ReplicationLatency , PendingObjects , PendingBytes ) for compliance tracking.
S3 Batch Replication: Allows data engineers to replicate existing objects created prior to the configuration of a CRR rule, or objects that previously failed replication.
Delete Marker Replication: Can be disabled to prevent accidental or malicious object deletion in the source bucket from propagating to the DR bucket.
4. Database Cross-Region Replication Mechanisms
Analytical and transactional databases require specialized replication architectures to enforce tight RPO boundaries during regional failures.
Amazon Aurora Global Databases
For high-performance OLTP applications, Aurora Global Databases decouple database compute from storage replication:
Dedicated storage-level replication infrastructure handles cross-Region data transport with zero impact on primary compute performance.
Typically delivers cross-Region replication latency under 1 second , but RPO during an unplanned outage depends on observed replication lag.
Supports up to 10 secondary Regions, subject to engine-version and Region support; per-cluster replica quotas must be checked for the selected engine.
Provides planned switchover for coordinated role changes and unplanned failover for outages; recovery time and possible data loss depend on topology, lag, and the failure. # AWS CLI command to execute managed failover for an Aurora Global Database
- aws rds failover-global-cluster \
- -global-cluster-identifier enterprise-aurora-global-db \
- -target-db-cluster-identifier arn:aws:rds:us-west-2:111122223333:cluster:aurora-dr-secondary-cluster
- Amazon DynamoDB Global Tables
DynamoDB Global Tables provide a fully managed, multi-Region, active-active database replication framework:
Utilizes DynamoDB Streams under the hood to propagate write operations across replica tables in target Regions.
Employs Last-Writer-Wins (LWW) timestamp resolution to reconcile concurrent writes occurring in different Regions.
Applications can read and write locally in any participating Region, offering near-zero RTO and minimal latency for globally distributed data pipelines.
Amazon Redshift Cross-Region Snapshot Copy
For analytical data warehouses, Amazon Redshift supports Automated Cross-Region Snapshot Copy :
Redshift automatically copies cluster snapshots to a secondary Region as soon as they are taken.
KMS master keys in the destination Region are mapped to encrypt the snapshot data in the target location.
In a DR event, a replacement Redshift cluster or Redshift Serverless namespace is restored directly from the copied snapshot.