AWS AmazonElastiCache: Exclude distributed KV caching clusters from automatic backups
Summary
Updates the automatic backups description to state that distributed KV caching clusters (cache.i8ge.48xlarge) are excluded from automatic backups, with a link to the distributed KV caching limits.
Security assessment
The edit documents a functional limitation (no automatic backups for a node type), which affects data-loss recovery but is not a security control or vulnerability fix.
Evidence
+You can enable automatic backups for any Valkey or Redis OSS serverless cache or node-based cluster, except distributed KV caching clusters (`cache.i8ge.48xlarge`). For more information, see [Requirements and limits for distributed KV caching](./distributed-kv-caching-limits.html). When automatic backups are enabled, ElastiCache creates a backup of the cache on a daily basis. There is no impact on the cache and the change is immediate. Automatic backups can help guard against data loss. In the event of a failure, you can create a new cache, restoring your data from the most recent backup. The result is a warm-started cache, preloaded with your data and ready for use. For more information, see [Restoring from a backup into a new cache](./backups-restoring.html).
Diff
diff --git a/AmazonElastiCache/latest/dg/backups-automatic.md b/AmazonElastiCache/latest/dg/backups-automatic.md index b032d6d..f632ff1 100644 --- a//AmazonElastiCache/latest/dg/backups-automatic.md +++ b//AmazonElastiCache/latest/dg/backups-automatic.md @@ -9 +9 @@ -You can enable automatic backups for any Valkey or Redis OSS serverless cache or node-based cluster. When automatic backups are enabled, ElastiCache creates a backup of the cache on a daily basis. There is no impact on the cache and the change is immediate. Automatic backups can help guard against data loss. In the event of a failure, you can create a new cache, restoring your data from the most recent backup. The result is a warm-started cache, preloaded with your data and ready for use. For more information, see [Restoring from a backup into a new cache](./backups-restoring.html). +You can enable automatic backups for any Valkey or Redis OSS serverless cache or node-based cluster, except distributed KV caching clusters (`cache.i8ge.48xlarge`). For more information, see [Requirements and limits for distributed KV caching](./distributed-kv-caching-limits.html). When automatic backups are enabled, ElastiCache creates a backup of the cache on a daily basis. There is no impact on the cache and the change is immediate. Automatic backups can help guard against data loss. In the event of a failure, you can create a new cache, restoring your data from the most recent backup. The result is a warm-started cache, preloaded with your data and ready for use. For more information, see [Restoring from a backup into a new cache](./backups-restoring.html).