AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Clarify migration prerequisites and source AUTH requirement

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

File: AmazonElastiCache/latest/dg/Migration-Prepare.md · Type: auth

Summary

Clarifies supported Valkey/Redis OSS versions, states the source cluster should not have AUTH enabled, and fixes command-renaming wording.

Security assessment

The changed AUTH prerequisite is security-adjacent because it documents an authentication configuration constraint for migration, but it does not address a specific vulnerability or incident.

Evidence

     * Your source Valkey or Redis OSS cluster should not have AUTH enabled.

Diff

diff --git a/AmazonElastiCache/latest/dg/Migration-Prepare.md b/AmazonElastiCache/latest/dg/Migration-Prepare.md
index dd761b8..68a665f 100644
--- a//AmazonElastiCache/latest/dg/Migration-Prepare.md
+++ b//AmazonElastiCache/latest/dg/Migration-Prepare.md
@@ -9,3 +9 @@
-With these steps you can prepare to migrate your data from a self-hosted Valkey or Redis source on EC2 to ElastiCache.
-
-This refers to migration from a self-hosted instance to the ElastiCache service. For information on upgrading from Redis OSS to Valkey on ElastiCache see [Upgrading engine versions including cross engine upgrades](./VersionManagement.HowTo.html).
+With these steps you can prepare to migrate your data from a self-managed Valkey or Redis OSS source on Amazon EC2 to a node-based ElastiCache cluster.
@@ -15 +13 @@ You must ensure that all four of the prerequisites mentioned following are satis
-###### To prepare your source and target Valkey or Redis OSS Nodes for migration
+###### To prepare your source and target Valkey or Redis OSS nodes for migration
@@ -21 +19 @@ An existing or newly created ElastiCache deployment should meet the following re
-     * It is using Valkey, or Redis OSS 5.0.6 or higher.
+     * It is using Valkey, or Redis OSS 5.0.5 or higher for cluster mode disabled or 5.0.6 or higher for cluster mode enabled.
@@ -29 +27 @@ An existing or newly created ElastiCache deployment should meet the following re
-     * For cluster-mode disabled, you can migrate directly from any supported Valkey or Redis OSS version to Valkey or Redis OSS version 5.0.6 onward, using the CLI or console. For cluster mode enabled, you can migrate directly from any cluster-mode enabled Valkey or Redis OSS version to Valkey or Redis OSS version 5.0.6 onward, using the CLI or console.
+     * For cluster-mode disabled, you can migrate directly from any supported Valkey or Redis OSS version to Valkey or Redis OSS version 5.0.5 onward, using the CLI or console. For cluster mode enabled, you can migrate directly from any cluster-mode enabled Valkey or Redis OSS version to Valkey or Redis OSS version 5.0.6 onward, using the CLI or console.
@@ -37 +35 @@ An existing or newly created ElastiCache deployment should meet the following re
-  2. Make sure that the configurations of your open-source Valkey or Redis OSS and the ElastiCache deployment are compatible. 
+  2. Make sure that the configurations of your Valkey or Redis OSS and the ElastiCache deployment are compatible. 
@@ -41 +39 @@ At a minimum, all the following in the target ElastiCache deployment should be c
-     * Your cluster should not have AUTH enabled.
+     * Your source Valkey or Redis OSS cluster should not have AUTH enabled.
@@ -49 +47 @@ At a minimum, all the following in the target ElastiCache deployment should be c
-     * Valkey or Redis OSS commands that perform data modification should not be renamed to allow replication of the data to succeed. for example `sync`, `psync`, `info`, `config`, `command`, and `cluster`.
+     * Valkey or Redis OSS commands that perform data modification should not be renamed to allow replication of the data to succeed. For example, `sync`, `psync`, `info`, `config`, `command`, and `cluster`.
@@ -76 +74 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Online migration for Valkey or Redis OSS
+Online migration to ElastiCache node-based clusters