AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Add TLS, auth, and CLI prerequisites to serverless migration guide

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

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

Summary

Expands the online migration to ElastiCache Serverless procedure: adds prerequisites for target users (same names, passwords, permissions), three subnets in different AZs, and AWS CLI 2.38.3+; clarifies that the migration endpoint only accepts connections in the Ready to sync state; instructs users to connect with TLS, allow the application in the target cache's security group, and verify routing by reading a source key before shifting traffic; reorders force-complete guidance; and adds a full AWS CLI walkthrough (prepare/describe/start/complete-migration).

Security assessment

The added text documents security-relevant operational guidance for migration: replicating authentication users/permissions on the target, connecting to the migration endpoint with TLS, restricting access via the target cache's security group, and verifying that reads return source values before moving traffic. It is best-practice hardening documentation rather than a fix for a specific vulnerability or incident, so it is not security_issue_related.

Evidence

+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. Update your application to connect to the migration endpoint. Connect with TLS, and allow your application in your target cache's security group.

Diff

diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md b/AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
index 2a860da..fb99291 100644
--- a//AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
+++ b//AmazonElastiCache/latest/dg/migration-to-serverless-procedure.md
@@ -24,0 +25,2 @@ 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).
+
@@ -26,0 +29,4 @@ Confirm that you have the following:
+  * At least three subnets in different Availability Zones for your target cache, each with free IP addresses.
+
+  * AWS CLI version 2.38.3 or later, if you use the AWS CLI.
+
@@ -82,0 +89,2 @@ 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.
+
@@ -85 +93,3 @@ While ElastiCache prepares the migration, **Current state** reads **Preparing mi
-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. Update your application to connect to the migration endpoint. To copy the address, choose **Copy migration endpoint**. 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.
+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**.
+
+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. 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.
@@ -106 +116 @@ 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**. 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. 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.
@@ -123,0 +134,2 @@ During cutover, **Current state** reads **Cutover in progress** and the banner r
+For most of the **Cutover in progress** state, ElastiCache is removing the migration infrastructure, and your traffic is already on your target cache.
+
@@ -132 +144 @@ 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, you must move your application traffic back to it yourself.
+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.
@@ -137,0 +150,46 @@ 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 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).
+    
+        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.
+
+  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.
+    
+        aws elasticache describe-serverless-caches \
+        --serverless-cache-name my-cache \
+        --query "ServerlessCaches[0].[Status,Migration.Status]" \
+        --output text
+
+  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 describe-serverless-caches \
+        --serverless-cache-name my-cache \
+        --query "ServerlessCaches[0].Migration.MigrationEndpoint"
+
+  4. 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
+
+  5. Check the migration state with the command from step 2 until it returns `migrating` and `syncing`.
+
+  6. Complete the migration. Skip this step if you chose automatic cutover.
+    
+        aws elasticache complete-migration \
+        --serverless-cache-name my-cache
+
+  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`.
+
+
+
+