AWS announces Multi-AZ with Standby for Amazon OpenSearch Service

Today, Amazon OpenSearch Service announces Multi-AZ with Standby, a new deployment option that enables 99.99% availability and consistent performance for business-critical workloads. With Multi-AZ with Standby, OpenSearch Service domains are resilient to potential infrastructure failures, such as a node or an Availability Zone (AZ) failure. Multi-AZ with Standby also ensures OpenSearch Service domains follow recommended best practices, simplifying configuration and management.

When Multi-AZ with Standby is enabled, OpenSearch Service reserves nodes in one of the AZs as standby; these nodes do not serve search requests and are primarily used for failover. Amazon OpenSearch Service monitors the underlying infrastructure for failures, and when a failure is identified, automatically promotes the standby nodes to active in less than a minute. OpenSearch Service continues to serve indexing and search requests, and any impact is limited to the time it takes to perform the failover. With Multi-AZ with Standby, there is no re-distribution of data or resources during a failure, thereby ensuring that cluster performance is unaffected during a failover.

When creating or updating an existing Managed Cluster, customers can enable the Multi-AZ with Standby deployment option using the AWS Console, command line interface (CLI), or the AWS software development kit (AWS SDK). Multi-AZ with Standby is available for OpenSearch versions 1.3 and above. For information on Multi-AZ with Standby for Amazon OpenSearch Service, please see documentation.

Multi-AZ for Standby is now available on Amazon OpenSearch Service in all AWS regions globally where Amazon OpenSearch service is available, except US West (N. California), AWS GovCloud (US-East), and AWS GovCloud (US-West). Please refer to the AWS Region Table for more information about Amazon OpenSearch Service availability.

To learn more about Amazon OpenSearch Service, please visit the product page.