ElastiCache Replication (Redis)
Single-node Amazon ElastiCache Redis clusters are in-memory entities with limited data protection services (AOF). if your cluster fails for any reason, you risk lose all the cluster's data. However, if you're running the Redis engine, you can group 2 to 6 nodes into a cluster with replicas where 1 to 5 read-only clusters contain replicate data of the group's single read/write primary. In this scenario, if one cluster fails for any reason you do not lose all your data since it is replicated in one or more other clusters.
As seen in the following graphic, the replication structure is contained within a shard (called node group in the API/CLI) which is contained within a Redis cluster. Redis (cluster mode disabled) clusters always have one shard. Redis (cluster mode enabled) clusters can have up to 15 shards with the cluster's data partitioned across the shards.
Redis cluster with replica nodes
If the cluster with replicas has Multi-AZ with automatic failover enabled and the primary fails, the primary fails over to a read replica. Because the data is updated on the replica nodes asynchronously, there may be some data loss due to latency in updating the replica nodes. For more information, see Mitigating Failures when Running Redis.
- Redis Replication
- Replication: Redis (cluster mode disabled) vs. Redis (cluster mode enabled)
- Replication: Multi-AZ with Automatic Failover (Redis)
- How Synchronization and Backup are Implemented
- Creating a Redis Cluster with Replicas
- Viewing a Replication Group's Details
- Finding Replication Group Endpoints
- Modifying a Cluster with Replicas
- Deleting a Cluster with Replicas
- Adding a Read Replica to a Redis Cluster
- Promoting a Read-Replica to Primary
- Deleting a Read Replica