AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Restructure ElastiCache Serverless migration procedure doc

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

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

Summary

Reorganizes the online migration procedure into clearer sections (Before you start, Creating the migration, Redirecting your application, Starting the data sync, Cutting over, Validating and cleaning up, Additional resources), adds console and AWS CLI steps, cutover-mode comparison table, and application-visible cutover behavior. Security-relevant content covers source authentication (existing/new Secrets Manager secret with customer managed KMS key, or none), TLS Verify CA with CA certificates, and cleanup of security group rules and secrets.

Security assessment

The diff is a documentation restructure of the migration procedure, not a fix for a specific vulnerability. It does document security-relevant configuration and hygiene: source authentication via Secrets Manager with a customer managed KMS key, TLS Verify CA with PEM CA certificates, and post-migration cleanup steps such as removing the source security group inbound rule and deleting the secret and KMS key. These are best-practice/hardening guidance rather than a response to an incident.

Evidence

     * **Create and use a new secret** – Enter a user name if your engine version uses one, enter a password, and choose a customer managed AWS KMS key. ElastiCache creates the secret. The user name and password must meet the requirements in [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).

Diff

diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md b/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
index c461f13..489789f 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 stop
+Before you startCreating the migrationRedirecting your applicationStarting the data syncCutting overCleaning upAdditional resources
@@ -9 +9 @@ Before you startCreate the migrationThe migration details pageRedirect your appl
-# Migrate your data to ElastiCache Serverless
+# Migrating your data to ElastiCache Serverless
@@ -15 +15 @@ This page walks you through an online migration from a self-managed Valkey or Re
-Before you begin, confirm that your source cache and your target cache meet the migration requirements. For more information, see [Prerequisites for online migration to ElastiCache Serverless](./migration-to-serverless-prerequisites.html). If your source requires authentication or TLS, set that up first. For more information, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+Confirm the following:
@@ -17 +17 @@ Before you begin, confirm that your source cache and your target cache meet the
-Before you migrate, test your workload on an ElastiCache Serverless cache to see how it scales and how many ElastiCache Processing Units (ECPUs) it consumes. For more information, see [Scaling ElastiCache Serverless clusters](./Scaling-serverless.html).
+  * Before you begin, confirm that your source cache and your target cache meet the migration requirements. For more information, see [Prerequisites and limitations for online migration to ElastiCache Serverless](./migration-to-serverless-prerequisites.html).
@@ -19 +19,3 @@ Before you migrate, test your workload on an ElastiCache Serverless cache to see
-Confirm that you have the following:
+  * If your source requires authentication or TLS, set that up first. For more information, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+
+  * Before you migrate, test your workload on an ElastiCache Serverless cache to see how it scales and how many ElastiCache Processing Units (ECPUs) it consumes. For more information, see [Scaling ElastiCache Serverless clusters](./Scaling-serverless.html).
@@ -23 +25,5 @@ Confirm that you have the following:
-  * A self-managed Valkey or Redis OSS source on Amazon EC2 that meets the source requirements.
+  * Confirm that you have a self-managed Valkey or Redis OSS source on Amazon EC2 that meets the source requirements.
+
+  * Confirm that you have a AWS Secrets Manager secret that holds your source credentials, if your source requires authentication.
+
+  * Confirm that your application's users are set up on your target cache, with the same user names, passwords, and permissions as on your source, if your source requires authentication. For more information about setting up target users, see [Setting up your application's users on your target](./migration-to-serverless-auth.html#migration-to-serverless-auth-target-users).
@@ -25 +31 @@ Confirm that you have the following:
-  * A Secrets Manager secret that holds your source credentials, if your source requires authentication.
+  * Confirm that you have your source TLS configuration, if your source requires TLS.
@@ -27 +33 @@ Confirm that you have the following:
-  * Your application's users set up on your target cache, with the same user names, passwords, and permissions as on your source, if your source requires authentication. For more information about setting up target users, see [Setting up your application's users on your target](./migration-to-serverless-auth.html#migration-to-serverless-auth-target-users).
+  * Confirm that you have at least three subnets in different Availability Zones for your target cache, each with free IP addresses.
@@ -29 +35 @@ Confirm that you have the following:
-  * Your source TLS configuration, if your source requires TLS.
+  * Confirm that you have AWS CLI version 2.38.3 or later, if you use the AWS CLI.
@@ -31 +36,0 @@ Confirm that you have the following:
-  * At least three subnets in different Availability Zones for your target cache, each with free IP addresses.
@@ -33 +37,0 @@ Confirm that you have the following:
-  * AWS CLI version 2.38.3 or later, if you use the AWS CLI.
@@ -35,0 +40 @@ Confirm that you have the following:
+## Creating the migration
@@ -36,0 +42 @@ Confirm that you have the following:
+You can create a migration with the ElastiCache console or the AWS CLI.
@@ -38 +44 @@ Confirm that you have the following:
-## Create the migration
+###### To create the migration (console)
@@ -40 +46 @@ Confirm that you have the following:
-You can create a migration with the ElastiCache console or the AWS CLI. You can open the **Create migration** page in two ways.
+  1. Open the **Create migration** page in one of the following ways:
@@ -45,0 +52 @@ You can create a migration with the ElastiCache console or the AWS CLI. You can
+  2. 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.
@@ -46,0 +54 @@ You can create a migration with the ElastiCache console or the AWS CLI. You can
+  3. For **Port** , enter your source port.
@@ -47,0 +56 @@ You can create a migration with the ElastiCache console or the AWS CLI. You can
+  4. For **Authentication method** , choose one of the following options.
@@ -49 +58 @@ You can create a migration with the ElastiCache console or the AWS CLI. You can
-On the **Create migration** page, complete the following steps.
+     * **Use an existing secret** – Choose your secret under **Existing secret**.
@@ -51 +60 @@ 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. 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.
+     * **Create and use a new secret** – Enter a user name if your engine version uses one, enter a password, and choose a customer managed AWS KMS key. ElastiCache creates the secret. The user name and password must meet the requirements in [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
@@ -53 +62 @@ On the **Create migration** page, complete the following steps.
-  2. For **Port** , enter your source port.
+     * **None** – Your source does not require authentication.
@@ -55 +64 @@ On the **Create migration** page, complete the following steps.
-  3. For **Authentication method** , choose one of the following options.
+  5. For **TLS encryption** , choose **Verify CA** or **None**.
@@ -57 +66 @@ On the **Create migration** page, complete the following steps.
-**Use an existing secret**
+If you choose **Verify CA** , under **Certificate authority** choose **Public CA** or **Private CA** , and provide the PEM-encoded CA certificates that issued your source's server certificate. Provide them for public and private authorities alike. For more information about why, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
@@ -58,0 +68 @@ On the **Create migration** page, complete the following steps.
+Warning
@@ -60 +70 @@ On the **Create migration** page, complete the following steps.
-Choose your secret under **Existing secret**.
+Your target cache must be empty when you create the migration. If it contains any keys, the prepare step fails and the target's **Events** tab shows "The serverless cache must have no keys before migration can begin." To empty the target, run `FLUSHALL` on it before you create the migration. `FLUSHALL` removes every key in the cache. You can have ElastiCache clear the target for you only when you start the data sync.
@@ -62 +72 @@ Choose your secret under **Existing secret**.
-**Create and use a new secret**
+  6. Under **Target details** , for **Choose target cache** , choose your cache. Only compatible caches are listed.
@@ -63,0 +74 @@ Choose your secret under **Existing secret**.
+  7. Choose **Create**. The migration details page opens. Its title is **Migration:** followed by your cache name.
@@ -65 +76 @@ Choose your secret under **Existing secret**.
-Enter a user name if your engine version uses one, enter a password, and choose a customer managed AWS KMS key. ElastiCache creates the secret. The user name and password must meet the requirements in [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+The migration details page shows the state and controls for your migration. The **Migration overview** shows **Target cache** , **Current state** , **Migration endpoint** , and **Cutover method**. The page has a **Monitor** tab and an **Events** tab. It also has **Stop** , **Force complete** , and **Start migration** buttons. While ElastiCache prepares the migration, **Current state** reads **Preparing migration** , and the **Migration endpoint** field is hidden. How long the prepare step takes depends on the size of your source. While **Current state** reads **Preparing migration** , the step is still running.
@@ -67 +78 @@ Enter a user name if your engine version uses one, enter a password, and choose
-**None**
+  8. Wait until the **Current state** is **Ready to sync**. The **Migration endpoint** field shows the address.
@@ -70 +80,0 @@ Enter a user name if your engine version uses one, enter a password, and choose
-Your source does not require authentication.
@@ -72 +81,0 @@ Your source does not require authentication.
-  4. For **TLS encryption** , choose **Verify CA** or **None**.
@@ -74 +83 @@ Your source does not require authentication.
-If you choose **Verify CA** , under **Certificate authority** choose **Public CA** or **Private CA** , and provide the PEM-encoded CA certificates that issued your source's server certificate. Provide them for public and private authorities alike. For more information about why, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+###### To create the migration (AWS CLI)
@@ -76 +85 @@ If you choose **Verify CA** , under **Certificate authority** choose **Public CA
-  5. Important
+  1. Enter the following AWS CLI command to prepare the migration, where ``my-cache`` is the name of your target cache and where ``192.0.2.10`` and ``6379`` are the private address and port of one node in your source:
@@ -78 +87,3 @@ If you choose **Verify CA** , under **Certificate authority** choose **Public CA
-Your target cache must be empty when you create the migration. If it contains any keys, the prepare step fails and the target's Events tab shows "The serverless cache must have no keys before migration can begin." To empty the target, run `FLUSHALL` on it before you create the migration. `FLUSHALL` removes every key in the cache. You can have ElastiCache clear the target for you only when you start the data sync.
+        aws elasticache prepare-migration \
+        --serverless-cache-name my-cache \
+        --customer-node-endpoint-list "Address='192.0.2.10',Port=6379"
@@ -80 +91 @@ Your target cache must be empty when you create the migration. If it contains an
-Under **Target details** , for **Choose target cache** , choose your cache. Only compatible caches are listed.
+For the authentication and TLS options, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
@@ -82 +93 @@ Under **Target details** , for **Choose target cache** , choose your cache. Only
-  6. Choose **Create**.
+  2. Wait until the migration state is `ready-to-sync`. For information about checking the migration state, see [Checking status and events using the AWS CLI](./migration-to-serverless-monitoring.html#migration-to-serverless-monitoring-cli).
@@ -87 +98 @@ Under **Target details** , for **Choose target cache** , choose your cache. Only
-The console opens the migration details page. Its title reads **Migration:** followed by your cache name.
+## Redirecting your application
@@ -89 +100 @@ The console opens the migration details page. Its title reads **Migration:** fol
-###### To do this with the AWS CLI
+Starting the data sync first does not affect the data on your target. Your traffic is routed to your source until cutover.
@@ -91 +102 @@ The console opens the migration details page. Its title reads **Migration:** fol
-  * Prepare the migration. For the authentication and TLS options, see [Source authentication for online migration to ElastiCache Serverless](./migration-to-serverless-auth.html).
+Warning
@@ -93,3 +104 @@ The console opens the migration details page. Its title reads **Migration:** fol
-        aws elasticache prepare-migration \
-        --serverless-cache-name my-cache \
-        --customer-node-endpoint-list "Address='10.0.0.10',Port=6379"
+Point your application at the migration endpoint only when the migration state is **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.
@@ -97 +106 @@ The console opens the migration details page. Its title reads **Migration:** fol
-Where:
+Note
@@ -99 +108 @@ Where:
-    * `my-cache` is the name of your target cache.
+A client that still connects straight to your source after cutover writes to a cache that no longer replicates to your target.
@@ -101 +110 @@ Where:
-    * `10.0.0.10` and `6379` are the private address and port of one node in your source.
+###### To redirect the application (console)
@@ -102,0 +112 @@ Where:
+  1. Choose **Copy migration endpoint**. This copies the endpoint address.
@@ -103,0 +114 @@ Where:
+  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).
@@ -104,0 +116 @@ Where:
+  3. Read a key that exists on your source through the migration endpoint, and confirm that it returns the value from your source.
@@ -106 +117,0 @@ Where:
-To check the migration state, see [Migration states](./migration-to-serverless.html#migration-to-serverless-states).
@@ -108 +118,0 @@ To check the migration state, see [Migration states](./migration-to-serverless.h
-## The migration details page
@@ -110 +119,0 @@ To check the migration state, see [Migration states](./migration-to-serverless.h
-The migration details page shows the state and controls for your migration. The **Migration overview** shows **Target cache** , **Current state** , **Migration endpoint** , and **Cutover method**. The page has a **Monitor** tab and an **Events** tab. It also has **Stop** , **Force complete** , and **Start migration** buttons.
@@ -112 +121 @@ 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.
+###### To redirect the application (AWS CLI)
@@ -114 +123 @@ While ElastiCache prepares the migration, **Current state** reads **Preparing mi
-How long the prepare step takes depends on the size of your source. While **Current state** reads **Preparing migration** , the step is still running.
+  1. 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.
@@ -116 +125,3 @@ How long the prepare step takes depends on the size of your source. While **Curr
-## Redirect your application
+        aws elasticache describe-serverless-caches \
+        --serverless-cache-name my-cache \
+        --query "ServerlessCaches[0].Migration.MigrationEndpoint"
@@ -118 +129 @@ How long the prepare step takes depends on the size of your source. While **Curr
-Warning
+  2. To check the migration state, see [Checking status and events using the AWS CLI](./migration-to-serverless-monitoring.html#migration-to-serverless-monitoring-cli).
@@ -120 +130,0 @@ 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.
@@ -122 +131,0 @@ Point your application at the migration endpoint only when Current state reads R
-When **Current state** reads **Ready to sync** , the **Migration endpoint** field shows the address.
@@ -124 +132,0 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
-  1. To copy the address, choose **Copy migration endpoint**.
@@ -126 +134 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
-  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).
+## Starting the data sync
@@ -128 +136 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
-  3. Read a key that exists on your source through the migration endpoint, and confirm that it returns the value from your source.
+When you start the data sync, ElastiCache begins replicating data from your source to your target cache. Your application continues to be served throughout. For more information about cutover modes, see Cutting over.
@@ -129,0 +138 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
+Important
@@ -130,0 +140 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
+If your migration is using Auto-cutover, redirect your application before you start the data sync, because ElastiCache cuts over at the next fully synced window.
@@ -131,0 +142 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
+###### To start the data sync (console)
@@ -133 +144 @@ When **Current state** reads **Ready to sync** , the **Migration endpoint** fiel
-Starting the data sync first does not affect the data on your target. Your traffic is routed to your source until cutover.
+  1. On the migration details page, choose **Start migration**.
@@ -135 +146 @@ Starting the data sync first does not affect the data on your target. Your traff
-Important
+  2. In the **Start migration** dialog box, for **Cutover mode** , choose **Manual cutover** or **Auto-cutover**. For more information, see Cutting over.
@@ -137 +148 @@ 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.
+  3. Under **Target cache data** , to clear a target that contains data, select **Authorize automatic clearing of the target cache if it contains data**. Your target contains data if you are starting the data sync again after you stopped it. It can also contain data if an earlier start failed. If your target contains data and you do not select this option, the data sync fails because the target is not empty, and the migration returns to **Ready to sync**.
@@ -139 +150 @@ If you use Auto-cutover, redirect your application before you start the data syn
-Note
+Warning
@@ -141 +152 @@ Note
-A client that still connects straight to your source after cutover writes to a cache that no longer replicates to your target.
+Clearing the target cannot be undone.
@@ -143 +154 @@ A client that still connects straight to your source after cutover writes to a c
-###### To do this with the AWS CLI
+  4. Choose **Start migration**. The **Current state** changes to **Initializing sync** and then to **Data sync in progress**. The migration stays in **Initializing sync** until replication begins.
@@ -145 +155,0 @@ A client that still connects straight to your source after cutover writes to a c
-  * 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.
@@ -147,3 +156,0 @@ A client that still connects straight to your source after cutover writes to a c
-        aws elasticache describe-serverless-caches \
-        --serverless-cache-name my-cache \
-        --query "ServerlessCaches[0].Migration.MigrationEndpoint"