AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Restructure ElastiCache serverless migration guide, add CLI steps and TLS/security group guidance

Service: AmazonElastiCache · 2026-11-13 · Documentation medium

File: AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md · Type: encryption

Summary

Reorganizes the online migration procedure for ElastiCache Serverless: moves AWS CLI instructions inline with each console step (prepare-migration, describe-serverless-caches, start-migration, complete-migration, stop-migration --force), converts banner text into Warning/Important/Note callouts, adds a note that the source address must be a private IP or a host name resolvable via public DNS (VPC-only private DNS fails the prepare step), and adds explicit guidance to connect to the migration endpoint with TLS and allow the application in the target cache's security group.

Security assessment

The added step explicitly instructs users to connect to the migration endpoint with TLS and to scope access via the target cache's security group, which is security best-practice guidance for protecting in-transit cache traffic and limiting network exposure. The change is a documentation restructure rather than a fix for a specific vulnerability, so it is not security_issue_related, but it does add security documentation with medium security impact.

Evidence

+  2. Update your application to connect to the migration endpoint with TLS, and allow your application in your target cache's security group. For more information, see [Client configuration](./migration-to-serverless-prerequisites.html#migration-to-serverless-client-config).

Diff

diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md b/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
index 9400a03..6cb73b0 100644
--- a//AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
+++ b//AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
@@ -7 +7 @@
-Before you startCreate the migrationThe migration details pageRedirect your applicationStart the data syncComplete the cutoverIf you need to stopUsing the AWS CLI
+Before you startCreate the migrationThe migration details pageRedirect your applicationStart the data syncComplete the cutoverIf you need to stop
@@ -11 +11 @@ Before you startCreate the migrationThe migration details pageRedirect your appl
-This page walks you through an online migration from a self-managed Valkey or Redis OSS source on Amazon EC2 to an ElastiCache Serverless for Valkey cache. You use the ElastiCache console from start to finish. You create the migration, redirect your application to the migration endpoint, start the data sync, and complete the cutover.
+This page walks you through an online migration from a self-managed Valkey or Redis OSS source on Amazon EC2 to an ElastiCache Serverless for Valkey cache. You can use the ElastiCache console or the AWS CLI. You create the migration, redirect your application to the migration endpoint, start the data sync, and complete the cutover.
@@ -40 +40 @@ Confirm that you have the following:
-You create a migration with the ElastiCache console. You can open the **Create migration** page in two ways.
+You can create a migration with the ElastiCache console or the AWS CLI. You can open the **Create migration** page in two ways.
@@ -51 +51 @@ On the **Create migration** page, complete the following steps.
-  1. Under **Source details** , for **Server address** , enter your source address. You can also choose an Amazon EC2 instance from the suggestions, which fills in the address.
+  1. Under **Source details** , for **Server address** , enter your source address. You can also choose an Amazon EC2 instance from the suggestions, which fills in the address. For the source address, enter the private IP address of a source node, or a host name that resolves through public DNS. A host name that resolves only in your VPC's private DNS fails the prepare step.
@@ -88,0 +89,19 @@ The console opens the migration details page. Its title reads **Migration:** fol
+###### To do this with the AWS CLI
+
+  * Prepare the migration. For the authentication and TLS options, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+    
+        aws elasticache prepare-migration \
+        --serverless-cache-name my-cache \
+        --customer-node-endpoint-list "Address='10.0.0.10',Port=6379"
+
+Where:
+
+    * `my-cache` is the name of your target cache.
+
+    * `10.0.0.10` and `6379` are the private address and port of one node in your source.
+
+
+
+
+To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
+
@@ -93 +112 @@ The migration details page shows the state and controls for your migration. The
-While ElastiCache prepares the migration, **Current state** reads **Preparing migration** , and the **Migration endpoint** field is hidden. The banner reads "Step 1 of 3: Preparing migration" and "This may take a few minutes. Once complete, choose Start migration to begin the data sync. You can remain on this page or return later to continue."
+While ElastiCache prepares the migration, **Current state** reads **Preparing migration** , and the **Migration endpoint** field is hidden.
@@ -99 +118,9 @@ How long the prepare step takes depends on the size of your source. While **Curr
-While **Current state** reads **Preparing migration** , the migration endpoint does not accept connections. Before you prepare a migration, and after a prepare step that fails, the endpoint serves your target cache, which is empty. Point your application at the migration endpoint only when **Current state** reads **Ready to sync**.
+###### Warning
+
+Point your application at the migration endpoint only when Current state reads Ready to sync. While the migration is preparing, the endpoint does not accept connections. Before you prepare a migration, and after a prepare step that fails, the endpoint serves your target cache, which is empty.
+
+When **Current state** reads **Ready to sync** , the **Migration endpoint** field shows the address.
+
+  1. To copy the address, choose **Copy migration endpoint**.
+
+  2. Update your application to connect to the migration endpoint with TLS, and allow your application in your target cache's security group. For more information, see [Client configuration](./migration-to-serverless-prerequisites.html#migration-to-serverless-client-config).
@@ -101 +128,27 @@ While **Current state** reads **Preparing migration** , the migration endpoint d
-When **Current state** reads **Ready to sync** , the banner reads "Migration is ready to sync" and "Your migration endpoint is active and traffic is routed to your source. Update your application to point to the migration endpoint, then choose Start migration when ready." The **Migration endpoint** field now shows the address. The migration endpoint is your serverless cache's standard endpoint, so your application keeps using it after cutover. Update your application to connect to the migration endpoint. Connect with TLS, and allow your application in your target cache's security group. For more information, see [Client configuration](./migration-to-serverless-prerequisites.html#migration-to-serverless-client-config). To copy the address, choose **Copy migration endpoint**. Before you move all of your traffic, connect to the migration endpoint with TLS and read a key that exists on your source. When the read returns the value from your source, the endpoint is routing to your source. Your traffic is routed to your source until cutover. The console reminds you to do this before you start the data sync, because ElastiCache cannot detect whether your application has moved. Starting the data sync first does not affect the data on your target. If you use Auto-cutover, redirect your application before you start the data sync, because ElastiCache cuts over at the next fully synced window. A client that still connects straight to your source after cutover writes to a cache that no longer replicates to your target.
+  3. Read a key that exists on your source through the migration endpoint, and confirm that it returns the value from your source.
+
+
+
+
+Starting the data sync first does not affect the data on your target. Your traffic is routed to your source until cutover.
+
+###### Important
+
+If you use Auto-cutover, redirect your application before you start the data sync, because ElastiCache cuts over at the next fully synced window.
+
+###### Note
+
+A client that still connects straight to your source after cutover writes to a cache that no longer replicates to your target.
+
+###### To do this with the AWS CLI
+
+  * Get the migration endpoint and point your application at it. Connect with TLS. Before you move all of your traffic, read a key that exists on your source through the migration endpoint. When the read returns the value from your source, the endpoint is routing to your source.
+    
+        aws elasticache describe-serverless-caches \
+        --serverless-cache-name my-cache \
+        --query "ServerlessCaches[0].Migration.MigrationEndpoint"
+
+
+
+
+To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
@@ -122 +175,13 @@ Under **Target cache data** , to clear a target that contains data, select **Aut
-**Current state** moves to **Initializing sync** and then to **Data sync in progress**. The migration stays in **Initializing sync** until replication begins. While the data sync initializes, the banner reads "Step 2 of 3: Data sync is initiating". With Manual cutover it reads "Connecting to your source and initializing data sync. Once syncing begins, you can choose Complete migration and cutover will occur on the next fully synced window." With Auto-cutover it reads "Connecting to your source and initializing data sync. Once syncing begins, cutover will be performed automatically on the next fully synced window." When the data sync is running, the banner reads "Step 2 of 3: Data sync is in progress". With Manual cutover it reads "Choose Complete migration and cutover will occur on the next fully synced window." With Auto-cutover it reads "We will perform auto-cutover for you on the next fully synced window." The **Monitor** tab shows a selected set of the target cache's metrics.
+**Current state** moves to **Initializing sync** and then to **Data sync in progress**. The migration stays in **Initializing sync** until replication begins.
+
+###### To do this with the AWS CLI
+
+  * Start the data sync. To have ElastiCache cut over for you, add `--auto-cutover`, and redirect your application before you run this command.
+    
+        aws elasticache start-migration \
+        --serverless-cache-name my-cache
+
+
+
+
+To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
@@ -138 +203 @@ ElastiCache cuts over at the next fully synced window. **Complete migration** is
-During cutover, **Current state** reads **Cutover in progress** and the banner reads "Step 3 of 3: Cutover is in progress" and "Traffic is being switched from your source to the target cache. This might take a few minutes." **Stop** and **Force complete** are disabled during cutover.
+During cutover, **Current state** reads **Cutover in progress**. **Stop** and **Force complete** are disabled during cutover.
@@ -144 +209 @@ With Auto-cutover, the console opens the cache details page when the migration f
-## If you need to stop
+###### To do this with the AWS CLI
@@ -146 +211 @@ With Auto-cutover, the console opens the cache details page when the migration f
-To stop the data sync, choose **Stop** on the migration details page. **Stop** is available only while **Current state** reads **Data sync in progress**. While the data sync stops, **Current state** reads **Stopping** and the banner reads "Data sync is being stopped. Traffic continues through the migration endpoint. Once stopped, the migration will return to Ready to sync." For more information about what stopping does, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).
+  * Complete the migration. Skip this step if you chose automatic cutover.
@@ -148 +213,2 @@ To stop the data sync, choose **Stop** on the migration details page. **Stop** i
-###### Force complete
+        aws elasticache complete-migration \
+        --serverless-cache-name my-cache
@@ -150 +215,0 @@ To stop the data sync, choose **Stop** on the migration details page. **Stop** i
-Force complete ends the migration even if your target is not in sync with your source. Your migration endpoint then serves from your target, which can have incomplete data. To return to your source, move your application traffic back to it yourself before you force complete.
@@ -152 +216,0 @@ Force complete ends the migration even if your target is not in sync with your s
-To end a migration that has reported an error, use **Force complete**. It is available when **Current state** reads **Ready to sync** or **Data sync in progress**. The console shows "Force complete triggered for `name`." For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).
@@ -154 +217,0 @@ To end a migration that has reported an error, use **Force complete**. It is ava
-## Using the AWS CLI
@@ -156 +219 @@ To end a migration that has reported an error, use **Force complete**. It is ava
-Online migration to ElastiCache Serverless needs AWS CLI version 2.38.3 or later. For the parameters of each command, see [prepare-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/prepare-migration.html), [start-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/start-migration.html), [stop-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/stop-migration.html), and [complete-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/complete-migration.html) in the _AWS CLI Command Reference_.
+To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
@@ -158 +221 @@ Online migration to ElastiCache Serverless needs AWS CLI version 2.38.3 or later
-To migrate with the AWS CLI, run the following steps in order.
+After the migration completes, verify your data and clean up. For the steps, see [After cutover](./migration-to-serverless-cutover.html#migration-to-serverless-after-cutover).
@@ -160 +223 @@ To migrate with the AWS CLI, run the following steps in order.
-  1. Prepare the migration. For the authentication and TLS options, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+## If you need to stop
@@ -162,3 +225 @@ To migrate with the AWS CLI, run the following steps in order.
-        aws elasticache prepare-migration \
-        --serverless-cache-name my-cache \
-        --customer-node-endpoint-list "Address='10.0.0.10',Port=6379"
+To stop the data sync, choose **Stop** on the migration details page. **Stop** is available only while **Current state** reads **Data sync in progress**. While the data sync stops, **Current state** reads **Stopping**. For more information about what stopping does, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).
@@ -166 +227 @@ To migrate with the AWS CLI, run the following steps in order.
-Where:
+###### Force complete
@@ -168 +229 @@ Where:
-     * `my-cache` is the name of your target cache.
+Force complete ends the migration even if your target is not in sync with your source. Your migration endpoint then serves from your target, which can have incomplete data. To return to your source, move your application traffic back to it yourself before you force complete.
@@ -170 +231 @@ Where:
-     * `10.0.0.10` and `6379` are the private address and port of one node in your source.
+To end a migration that has reported an error, use **Force complete**. It is available when **Current state** reads **Ready to sync** or **Data sync in progress**. The console shows "Force complete triggered for `name`." For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).
@@ -172 +233 @@ Where:
-  2. Check the migration state until the command returns `migrating` and `ready-to-sync`. A larger source takes longer to prepare. While the migration reads `preparing`, the migration endpoint does not accept connections. If the command returns `available` and `None`, the prepare step failed and ElastiCache rolled the migration back. Read the target cache's events for the reason.
+###### To do this with the AWS CLI
@@ -174,4 +235 @@ Where:
-        aws elasticache describe-serverless-caches \
-        --serverless-cache-name my-cache \
-        --query "ServerlessCaches[0].[Status,Migration.Status]" \
-        --output text
+  1. To stop the data sync, run the following command.
@@ -179 +237,2 @@ Where:
-  3. Get the migration endpoint and point your application at it. Connect with TLS. Before you move all of your traffic, read a key that exists on your source through the migration endpoint. When the read returns the value from your source, the endpoint is routing to your source.
+        aws elasticache stop-migration \
+        --serverless-cache-name my-cache
@@ -181,3 +240 @@ Where:
-        aws elasticache describe-serverless-caches \
-        --serverless-cache-name my-cache \
-        --query "ServerlessCaches[0].Migration.MigrationEndpoint"
+Where:
@@ -185 +242 @@ Where:
-  4. Start the data sync. To have ElastiCache cut over for you, add `--auto-cutover`, and redirect your application before you run this command.
+     * `my-cache` is the name of your ElastiCache Serverless cache.
@@ -187,2 +244 @@ Where:
-        aws elasticache start-migration \
-        --serverless-cache-name my-cache
+  2. To end a migration that has reported an error instead, force complete it.
@@ -190 +246,3 @@ Where:
-  5. Check the migration state with the command from step 2 until it returns `migrating` and `syncing`.
+        aws elasticache complete-migration \
+        --serverless-cache-name my-cache \
+        --force
@@ -192 +250,3 @@ Where:
-  6. Complete the migration. Skip this step if you chose automatic cutover.
+Where:
+
+     * `my-cache` is the name of your ElastiCache Serverless cache.
@@ -194,2 +253,0 @@ Where:
-        aws elasticache complete-migration \
-        --serverless-cache-name my-cache
@@ -197 +254,0 @@ Where:
-  7. Check the migration state with the command from step 2 until it returns `available` and `None`. The cache returns to `available` after a successful migration, after a force complete, and after a failed prepare step, so confirm the result in the target cache's events. The last event of a successful migration reads Successfully completed the migration for serverless cache `my-cache`.
@@ -199,0 +257 @@ Where:
+To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
@@ -200,0 +259 @@ Where:
+For the parameters of each command, see [prepare-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/prepare-migration.html), [start-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/start-migration.html), [stop-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/stop-migration.html), and [complete-migration](https://docs.aws.amazon.com/cli/latest/reference/elasticache/complete-migration.html) in the _AWS CLI Command Reference_.