AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Clarify migration steps and correct security group inbound wording

Service: AmazonElastiCache · 2026-10-24 · Documentation low

File: AmazonElastiCache/latest/dg/Migration-Initiate.md · Type: network

Summary

Adds a warning that migration deletes existing target data and corrects the security group troubleshooting text from 'input bound' to 'inbound' traffic.

Security assessment

The changed line documents required inbound security group access from ElastiCache nodes, which is network security guidance, but it is a wording correction rather than a fix for a specific vulnerability.

Evidence

  * Ensure the security group attached to your Valkey or Redis OSS instances allows inbound traffic from ElastiCache nodes.

Diff

diff --git a/AmazonElastiCache/latest/dg/Migration-Initiate.md b/AmazonElastiCache/latest/dg/Migration-Initiate.md
index e3608a5..b2ee559 100644
--- a//AmazonElastiCache/latest/dg/Migration-Initiate.md
+++ b//AmazonElastiCache/latest/dg/Migration-Initiate.md
@@ -9 +9 @@
-After all prerequisites are complete, you can begin data migration using the AWS Management Console, ElastiCache API, or AWS CLI. For cluster-mode enabled, if slot migration differs, a resharding will be performed before live migration. The following example shows using the CLI.
+After all prerequisites are complete, you can begin migrating data to your node-based ElastiCache cluster using the AWS Management Console, ElastiCache API, or AWS CLI. For cluster-mode enabled, if slot migration differs, a resharding will be performed before live migration. The following example shows using the CLI.
@@ -13 +13,5 @@ After all prerequisites are complete, you can begin data migration using the AWS
-We recommended to use `TestMigration` API to validate migration setup. But this is strictly optional.
+We recommend that you validate your setup with the `TestMigration` API operation first. This step is optional.
+
+###### Important
+
+When the migration starts, ElastiCache deletes all existing data in the target cluster and replaces it with data from your source.
@@ -29 +33 @@ The following is an example using the CLI.
-As you run this command, the ElastiCache primary node (in each shard) configures itself to become a replica of your Valkey or Redis OSS instance (in corresponding shard owning same slots in cluster enabled redis). The status of ElastiCache cluster changes to **migrating** and data starts migrating from your Valkey or Redis OSS instance to the ElastiCache primary node. Depending on the size of the data and load on your Valkey or Redis OSS instance, the migration can take a while to complete. You can check the progress of the migration by running the [valkey-cli INFO](https://valkey.io/commands/info) command on your Valkey instance and ElastiCache primary node.
+As you run this command, the ElastiCache primary node (in each shard) configures itself to become a replica of your Valkey or Redis OSS instance (for cluster mode enabled, in the shard that owns the same slots). The status of ElastiCache cluster changes to **migrating** and data starts migrating from your Valkey or Redis OSS instance to the ElastiCache primary node. Depending on the size of the data and load on your Valkey or Redis OSS instance, the migration can take a while to complete. You can check the progress of the migration by running the [valkey-cli INFO](https://valkey.io/commands/info) command on your Valkey instance and ElastiCache primary node.
@@ -41 +45 @@ If an ElastiCache primary node can't become a replica of your Valkey or Redis OS
-  * Ensure the security group attached to your Valkey or Redis OSS instances allows input bound traffic from ElastiCache nodes.
+  * Ensure the security group attached to your Valkey or Redis OSS instances allows inbound traffic from ElastiCache nodes.