AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Rewrite ElastiCache console migration workflow and requirements

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

File: AmazonElastiCache/latest/dg/Migration-Console.md

Summary

Restructures the console-based data migration guide: narrows the scenario to self-managed Valkey/Redis OSS on EC2 as source, replaces the inline source-prerequisite list (engine version, AUTH, protected-mode, bind, databases, command renaming, resource sizing) with a pointer to Migration-Prepare.html, adds a Test migration option, details the Start/Stop migration UI paths, and adds a warning that starting migration deletes existing target data and that Force stop skips sync checks.

Security assessment

The security-relevant prerequisites that were removed from this page (AUTH disabled, protected-mode set to no, bind allowlist) are source-side self-managed hardening notes that have been relocated to Migration-Prepare.html, not a fix for a specific vulnerability. The newly added content is operational (Test migration, Start/Stop migration, target data being overwritten, Force stop bypassing sync validation), so no new security feature or vulnerability remediation is documented here.

Evidence

-     * Your cluster should not have AUTH enabled.

Diff

diff --git a/AmazonElastiCache/latest/dg/Migration-Console.md b/AmazonElastiCache/latest/dg/Migration-Console.md
index 399ac3c..b76af3f 100644
--- a//AmazonElastiCache/latest/dg/Migration-Console.md
+++ b//AmazonElastiCache/latest/dg/Migration-Console.md
@@ -9 +9 @@
-You can use the AWS Management Console to migrate your data from your cluster to your Valkey or Redis OSS cluster. 
+You can use the AWS Management Console to migrate your data from a self-managed Valkey or Redis OSS source on Amazon EC2 to a node-based ElastiCache cluster.
@@ -15 +15 @@ You can use the AWS Management Console to migrate your data from your cluster to
-  2. Either create a new Valkey or Redis OSS cluster or choose an existing cluster. Make sure that the cluster meets the following requirements:
+  2. Either create a new Valkey or Redis OSS cluster or choose an existing cluster. Make sure that your source and the cluster meet the requirements in [Preparing your source and target for migration](./Migration-Prepare.html), and that the following is true:
@@ -17,9 +17 @@ You can use the AWS Management Console to migrate your data from your cluster to
-     * Your engine version should be Valkey 7.2 and higher, or Redis OSS 5.0.6 or higher. 
-
-     * Your cluster should not have AUTH enabled.
-
-     * The config `protected-mode` should be set to `no`.
-
-     * If you have `bind` configuration in your Valkey or Redis OSS config, then it should be updated to allow requests from ElastiCache nodes.
-
-     * The number of databases should be the same between the ElastiCache node and your Valkey or Redis OSS cluster. This value is set using `databases` in the engine config.
+     * The cluster is in **available** status.
@@ -27 +19 @@ You can use the AWS Management Console to migrate your data from your cluster to
-     * Valkey or Redis OSS commands that perform data modification should not be renamed to allow replication of the data to succeed.
+  3. Open the migration form in one of the following ways:
@@ -29 +21 @@ You can use the AWS Management Console to migrate your data from your cluster to
-     * To replicate the data from your Valkey or Redis OSS cluster to ElastiCache, make sure that there is sufficient CPU and memory to handle this additional load. This load comes from the RDB file created by your Valkey or Redis OSS cluster and transferred over the network to ElastiCache node.
+     * In the navigation pane, choose **Migrations**. Choose **Create migration** , and then choose **Migrate to node-based**. On the **Migrate data from endpoint** page, for **Target ElastiCache cluster name** , choose your cluster.
@@ -31 +23 @@ You can use the AWS Management Console to migrate your data from your cluster to
-     * The cluster is in **available** status.
+     * In the cluster list, select your cluster. For **Actions** , choose **Migrate data from endpoint**. The **Migrate data to`cluster-name`?** dialog box opens with your cluster as the target.
@@ -33 +25 @@ You can use the AWS Management Console to migrate your data from your cluster to
-  3. With your cluster selected, choose **Migrate Data from Endpoint** for **Actions**. 
+Choosing **Start migration** on the cluster details page opens the same dialog box.
@@ -35 +27 @@ You can use the AWS Management Console to migrate your data from your cluster to
-  4. In the **Migrate Data from Endpoint** dialog box, enter the IP address, and the port where your Valkey or Redis OSS cluster is available.
+  4. For **Source endpoint** , enter the IP address of your source Valkey or Redis OSS cluster. For **Source port** , enter the port where your source is available.
@@ -41 +33 @@ The IP address must be exact. If you enter the address incorrectly, the migratio
-  5. Choose **Start Migration**.
+  5. (Optional) To validate your setup without migrating any data, choose **Test migration**. For more information, see [Testing the data migration](./Migration-Test.html).
@@ -43 +35 @@ The IP address must be exact. If you enter the address incorrectly, the migratio
-As the cluster begins migration, it changes to **Modifying** and then **Migrating** status.
+  6. ###### Important
@@ -45 +37 @@ As the cluster begins migration, it changes to **Modifying** and then **Migratin
-  6. Monitor the migration progress by choosing **Events** on the navigation pane.
+When the migration starts, ElastiCache deletes all existing data in the target cluster and replaces it with data from your source.
@@ -46,0 +39 @@ As the cluster begins migration, it changes to **Modifying** and then **Migratin
+Choose **Start migration**.
@@ -47,0 +41 @@ As the cluster begins migration, it changes to **Modifying** and then **Migratin
+As the cluster begins migration, it changes to **Modifying** and then **Migrating** status.
@@ -48,0 +43 @@ As the cluster begins migration, it changes to **Modifying** and then **Migratin
+  7. Monitor the migration progress by choosing **Events** on the navigation pane.
@@ -50 +44,0 @@ As the cluster begins migration, it changes to **Modifying** and then **Migratin
-At any point during the migration process, you can stop migration. To do so, choose your cluster and choose **Stop Data Migration** for **Actions**. The cluster then goes to **Available** status.
@@ -52 +45,0 @@ At any point during the migration process, you can stop migration. To do so, cho
-If the migration succeeds, the cluster goes to **Available** status and the event log shows the following:
@@ -54 +46,0 @@ If the migration succeeds, the cluster goes to **Available** status and the even
-`Migration operation succeeded for replication group `ElastiCacheClusterName`.`
@@ -56 +48 @@ If the migration succeeds, the cluster goes to **Available** status and the even
-If the migration fails, the cluster goes to **Available** status and the event log shows the following:
+At any point during the migration, you can stop it. In the cluster list, select your cluster. For **Actions** , choose **Stop data migration**. This option is available while the cluster is in **Migrating** status. In the **Stop data migration to`cluster-name`?** dialog box, choose **Stop data migration**.
@@ -58 +50 @@ If the migration fails, the cluster goes to **Available** status and the event l
-`Migration operation failed for replication group `ElastiCacheClusterName`.`
+Stopping the migration completes it, the same way as the `CompleteMigration` API operation. ElastiCache stops replicating from your source and promotes your ElastiCache cluster to primary. The data that already synced stays in the cluster, and writes that reach your source after that point aren't copied. If the data isn't in sync, the request can fail and the cluster stays in **Migrating** status. To stop without checking that the data is in sync, select **Force** under **Force migration stop**. For more information, see [Completing the data migration](./Migration-Complete.html). The cluster then goes to **Available** status.