AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Note data loss on node replace/reboot for distributed KV caching

Service: AmazonElastiCache · 2026-11-19 · Documentation low

File: AmazonElastiCache/latest/dg/ElastiCacheSNS.md

Summary

Adds notes to the CacheNodeReplaceComplete and CacheNodesRebooted SNS event descriptions stating that on distributed KV caching clusters a replaced or rebooted node loses all its objects, with links to resilience documentation.

Security assessment

The change only clarifies data-persistence behavior (objects lost on node replacement/reboot) for a new node type; it is operational guidance with no authentication, encryption, or exposure implications.

Evidence

+ElastiCache:CacheNodesRebooted |  `ElastiCache:CacheNodesRebooted : `cluster-name`` |  One or more cache nodes has been rebooted. On distributed KV caching clusters, a rebooted node loses all its objects. For more information, see [Resilience and data persistence](./distributed-kv-caching-how-it-works.html#distributed-kv-caching-how-it-works.resilience). Message (Memcached): `"Cache node %s shutdown"` Then a second message: `"Cache node %s restarted"`  

Diff

diff --git a/AmazonElastiCache/latest/dg/ElastiCacheSNS.md b/AmazonElastiCache/latest/dg/ElastiCacheSNS.md
index 2b289e6..29ba4c4 100644
--- a//AmazonElastiCache/latest/dg/ElastiCacheSNS.md
+++ b//AmazonElastiCache/latest/dg/ElastiCacheSNS.md
@@ -57,2 +57,2 @@ ElastiCache:CacheNodeReplaceStarted |  `ElastiCache:CacheNodeReplaceStarted : `c
-ElastiCache:CacheNodeReplaceComplete |  `ElastiCache:CacheNodeReplaceComplete : `cluster-name`` |  ElastiCache has detected that the host running a cache node is degraded or unreachable and has completed replacing the cache node. NoteThe DNS entry for the replaced cache node is not changed. In most instances, you do not need to refresh the server-list for your clients when this event occurs. However, some cache client libraries may stop using the cache node even after ElastiCache has replaced the cache node; in this case, the application should refresh the server-list when this event occurs.  
-ElastiCache:CacheNodesRebooted |  `ElastiCache:CacheNodesRebooted : `cluster-name`` |  One or more cache nodes has been rebooted. Message (Memcached): `"Cache node %s shutdown"` Then a second message: `"Cache node %s restarted"`  
+ElastiCache:CacheNodeReplaceComplete |  `ElastiCache:CacheNodeReplaceComplete : `cluster-name`` |  ElastiCache has detected that the host running a cache node is degraded or unreachable and has completed replacing the cache node. NoteThe DNS entry for the replaced cache node is not changed. In most instances, you do not need to refresh the server-list for your clients when this event occurs. However, some cache client libraries may stop using the cache node even after ElastiCache has replaced the cache node; in this case, the application should refresh the server-list when this event occurs. NoteOn distributed KV caching clusters, this event means that the node lost all its objects. For more information, see [Resilience and data persistence](./distributed-kv-caching-how-it-works.html#distributed-kv-caching-how-it-works.resilience).Service updates and engine upgrades also remove all stored objects. Apply updates in a maintenance window, and expect the cache to be empty after the update. For more information, see [Requirements and limits for distributed KV caching](./distributed-kv-caching-limits.html).  
+ElastiCache:CacheNodesRebooted |  `ElastiCache:CacheNodesRebooted : `cluster-name`` |  One or more cache nodes has been rebooted. On distributed KV caching clusters, a rebooted node loses all its objects. For more information, see [Resilience and data persistence](./distributed-kv-caching-how-it-works.html#distributed-kv-caching-how-it-works.resilience). Message (Memcached): `"Cache node %s shutdown"` Then a second message: `"Cache node %s restarted"`