Amazon OpenSearch Service now offers managed cross-Region disaster recovery, giving teams a way to protect search, AI and analytics workloads without building their own replication setup. AWS says the service targets a recovery point objective under one minute and a recovery time objective under 20 minutes.
AWS AI Watch analysis
What happened
Customers create OpenSearch domains in two Regions and pair them through the console or a single API call. The secondary domain stays continuously in sync with the primary. A planned switchover can exchange their roles with zero data loss; if the primary becomes unavailable, failover promotes the secondary, with potential data loss limited to replication lag.
The feature requires OpenSearch 3.7 or later and is available in commercial AWS Regions where OpenSearch Service is offered. AWS says UltraWarm storage and OpenSearch Optimized instances OR1 and OR2 are not supported. There is no additional charge for the feature itself, but customers pay for the secondary domain and cross-Region data transfer. See AWS’s announcement.
Why it matters
For teams running important search services, replication and recovery are not glamorous jobs, but a regional outage can make them everyone’s problem at once. A managed option could reduce the work involved in keeping a second domain current and switching over when trouble arrives.
The recovery targets are useful planning figures, not a promise that every workload will recover on that schedule. Teams still need to check whether their domain configuration is supported, and budget for the second domain and data transfer. The feature may simplify disaster recovery; it does not make the bill or the operational plan disappear.
Our read
This is a practical infrastructure improvement with clear stakes: AWS is offering a supported route to keep a second OpenSearch domain ready and cut over when needed. The sub-minute recovery-point target is especially notable, while the under-20-minute recovery-time target gives operators a concrete figure to assess against their own needs.
If you run OpenSearch, check your version and storage setup first, then compare the stated targets with your recovery requirements and the cost of running a second domain. Disaster recovery is at its best when the plan has already been tested, preferably before the incident decides to conduct the test for you.
What to watch
- Whether AWS publishes more detail on how the stated recovery targets apply to different workloads.
- How customers test failover and restore protection after a regional outage.
- Whether AWS expands support to UltraWarm storage or OR1 and OR2 instances.
Discussion spark: Would you pay to keep a second OpenSearch domain ready for a faster regional recovery, or is the added infrastructure cost hard to justify for your workloads?
Sources and evidence
- Amazon OpenSearch Service announces managed cross-Region disaster recovery (10 November 2026, 19:00 UTC)
- Amazon EC2 G7 instances now available in additional regions (10 November 2026, 19:00 UTC)
- AWS Billing and Cost Management now supports AWS Billing Conductor and AWS Billing Transfer views as source views for custom billing views (10 November 2026, 19:00 UTC)
- AWS Network Firewall launches next-generation firewall policy (10 November 2026, 19:00 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)