AWS Security ChangesHomeSearch

AWS AmazonElastiCache: ElastiCache Multi-AZ failover guidance rewritten for availability

Service: AmazonElastiCache · 2026-09-27 · Documentation low

File: AmazonElastiCache/latest/dg/disaster-recovery-resiliency.md

Summary

Rewrites the disaster recovery/resiliency page to recommend enabling Multi-AZ, clarifies automatic failover behavior with and without Multi-AZ, notes that replicas are not guaranteed to be in different AZs when Multi-AZ is off, and updates the failover step descriptions and cross-reference link.

Security assessment

The changed lines concern availability and failover topology (Multi-AZ, replica promotion, AZ distribution) rather than confidentiality, authentication, or a specific vulnerability. The note that replicas may not be in different AZs without Multi-AZ is a resiliency caveat, not a security fix, so this is a low-severity, non-security documentation update.

Evidence

We recommend enabling Multi-AZ on your Valkey or Redis OSS replication groups for the best availability configuration. Multi-AZ distributes your replicas across Availability Zones and enables automatic failover, so that a primary node failure results in rapid promotion of a replica with minimal write interruption.

Diff

diff --git a/AmazonElastiCache/latest/dg/disaster-recovery-resiliency.md b/AmazonElastiCache/latest/dg/disaster-recovery-resiliency.md
index 1ab88b64c..540ced5c1 100644
--- a//AmazonElastiCache/latest/dg/disaster-recovery-resiliency.md
+++ b//AmazonElastiCache/latest/dg/disaster-recovery-resiliency.md
@@ -107 +107 @@ During this time your application can continue reading and writing using the oth
-You can enable Multi-AZ on your Valkey or Redis OSS replication groups. Whether you enable Multi-AZ or not, a failed primary will be detected and replaced automatically. How this takes place varies whether or not Multi-AZ is or is not enabled.
+We recommend enabling Multi-AZ on your Valkey or Redis OSS replication groups for the best availability configuration. Multi-AZ distributes your replicas across Availability Zones and enables automatic failover, so that a primary node failure results in rapid promotion of a replica with minimal write interruption.
@@ -113 +113 @@ You can enable Multi-AZ on your Valkey or Redis OSS replication groups. Whether
-  2. ElastiCache promotes the read replica node with the least replication lag to primary node.
+  2. ElastiCache automatically promotes the read replica node with the least replication lag to primary node.
@@ -126 +126 @@ Failing over to a replica node is generally faster than creating and provisionin
-For more information, see [Minimizing downtime in ElastiCache by using Multi-AZ with Valkey and Redis OSS](./AutoFailover.html).
+For more information about how Multi-AZ and automatic failover work together, see [Automatic failover and Multi-AZ](./AutoFailover.html#AutoFailover.Understanding).
@@ -128 +128 @@ For more information, see [Minimizing downtime in ElastiCache by using Multi-AZ
-###### When Multi-AZ is disabled
+###### When Multi-AZ is not enabled
@@ -136 +136 @@ For more information, see [Minimizing downtime in ElastiCache by using Multi-AZ
-  4. ElastiCache syncs the new primary with one of the existing replicas.
+  4. If replicas exist, ElastiCache syncs the new primary with one of the existing replicas. If no replicas exist, the new primary starts empty.
@@ -138 +138 @@ For more information, see [Minimizing downtime in ElastiCache by using Multi-AZ
-  5. When the sync is finished, the new node functions as the cluster's primary node.
+  5. The new node functions as the cluster's primary node.
@@ -143 +143 @@ For more information, see [Minimizing downtime in ElastiCache by using Multi-AZ
-During steps 1 through 4 of this process, your application can't write to the primary node. However, your application can continue reading from your replica nodes.
+###### Note
@@ -145 +145,5 @@ During steps 1 through 4 of this process, your application can't write to the pr
-For added protection, we recommend that you launch the nodes in your replication group in different Availability Zones (AZs). If you do this, an AZ failure will only impact the nodes in that AZ and not the others.
+While it is possible to have automatic failover enabled without Multi-AZ, replicas are not guaranteed to be in different Availability Zones in this configuration. Failover still promotes a replica to primary if one is available, but this does not protect against AZ-level failures. For most use cases, we recommend enabling Multi-AZ.
+
+During steps 1 through 4 of this process, your application can't write to the primary node. However, if you have replica nodes, your application can continue reading from them during this process.
+
+For added protection, we recommend that you launch the nodes in your replication group in different Availability Zones (AZs) by enabling Multi-AZ. If you do this, an AZ failure will only impact the nodes in that AZ and not the others.