AWS AmazonElastiCache documentation change
Summary
Fixed typo in 'Redis OSS' engine name from 'Rediss' to 'Redis'
Security assessment
Minor typo correction with no security implications. No security context or vulnerabilities addressed.
Diff
diff --git a/AmazonElastiCache/latest/dg/Replication.md b/AmazonElastiCache/latest/dg/Replication.md index 89a7aba78..20b5ed035 100644 --- a//AmazonElastiCache/latest/dg/Replication.md +++ b//AmazonElastiCache/latest/dg/Replication.md @@ -7 +7 @@ -Single-node Amazon ElastiCache Valkey and Redis OSS clusters are in-memory entities with limited data protection services (AOF). If your cluster fails for any reason, you lose all the cluster's data. However, if you're running a Valkey or Rediss OSS engine, you can group 2 to 6 nodes into a cluster with replicas where 1 to 5 read-only nodes contain replicate data of the group's single read/write primary node. In this scenario, if one node fails for any reason, you do not lose all your data since it is replicated in one or more other nodes. Due to replication latency, some data may be lost if it is the primary read/write node that fails. +Single-node Amazon ElastiCache Valkey and Redis OSS clusters are in-memory entities with limited data protection services (AOF). If your cluster fails for any reason, you lose all the cluster's data. However, if you're running a Valkey or Redis OSS engine, you can group 2 to 6 nodes into a cluster with replicas where 1 to 5 read-only nodes contain replicate data of the group's single read/write primary node. In this scenario, if one node fails for any reason, you do not lose all your data since it is replicated in one or more other nodes. Due to replication latency, some data may be lost if it is the primary read/write node that fails.