Disaster-Recovery on CuraDevOps

AWS Elastic Disaster Recovery expands to six new regions

Thu, 23 Jul 2026 12:19:57 +0000

Platform/SRE — Learn: Relevant if you’re designing DR for workloads in Bangkok, Malaysia, New Zealand, Taipei, Calgary, or Mexico Central — DRS is now available in 36 regions, which may enable in-region DR targets previously requiring cross-region routing.
CI/CD — Skip
Leader — Learn: If the org has data-residency or latency requirements for any of these six new regions, this expands DR options worth noting in a future architecture review — no immediate decision required.

Thu, 16 Jul 2026 12:15:50 +0000

Platform/SRE — Plan: If you use AWS DRS for EC2 workloads, enabling this feature can meaningfully shrink your RTO with no added cost — evaluate enabling it account-wide or per server during your next DR review.
CI/CD — Skip
Leader — Learn: A no-cost RTO improvement of up to 65% on EC2 disaster recovery is worth noting when reviewing reliability targets and DR posture with engineering leadership.

Wed, 15 Jul 2026 12:10:55 +0000

Platform/SRE — Plan: Teams running I/O-intensive workloads (databases, etc.) on AWS DRS should evaluate setting an EBS initialization rate on DRS launch templates to reduce time-to-full-performance during recovery drills — no deadline, but worth scheduling as a DR configuration review this quarter.
CI/CD — Skip
Leader — Skip

Wed, 15 Jul 2026 12:10:55 +0000

Platform/SRE — Learn: Useful operational improvement for teams running Redshift Serverless with zero-ETL or S3 event integrations — snapshot restores within the same namespace no longer break integrations. No deadline or migration action required.
CI/CD — Skip
Leader — Skip