AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Editorial cleanup of ElastiCache serverless migration auth guidance

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

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

Summary

Restructures the three source-authentication method bullets, tightens wording about secret validation and required permissions, replaces example source node IP 10.0.0.10 with the documentation-reserved address 192.0.2.10, clarifies the valkey-cli access-control command, and removes the Related topics section/updates the prerequisites heading.

Security assessment

All hunks are wording/formatting or example-value changes to an existing page about Secrets Manager credentials, IAM read policy, and TLS in transit. The only security-adjacent edit is swapping the illustrative private address 10.0.0.10 for the RFC 5737 documentation range 192.0.2.10, a documentation hygiene improvement that avoids users copy-pasting a real private address; no new security feature, control, or vulnerability fix is introduced.

Evidence

+        --customer-node-endpoint-list "Address='192.0.2.10',Port=6379" \

Diff

diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-auth.md b/AmazonElastiCache/latest/dg/migration-to-serverless-auth.md
index 23bb077..5103b31 100644
--- a//AmazonElastiCache/latest/dg/migration-to-serverless-auth.md
+++ b//AmazonElastiCache/latest/dg/migration-to-serverless-auth.md
@@ -7 +7 @@
-Storing source credentialsPermissions for the migration userSetting up your application's users on your targetProviding the secret when you prepare a migrationEncryption in transitRelated topics
+Storing source credentialsPermissions for the migration userSetting up your application's users on your targetProviding the secret when you prepare a migrationEncryption in transit
@@ -23 +23 @@ In the console, you choose one of three authentication methods:
-Use an existing secret
+  * **Use an existing secret** – Choose an existing secret from Secrets Manager.
@@ -24,0 +25 @@ Use an existing secret
+  * **Create and use a new secret** – ElastiCache creates a secret to store your specified credentials.
@@ -26 +27 @@ Use an existing secret
-Choose an existing secret from Secrets Manager.
+  * **None** – Source doesn't require authentication.
@@ -28 +28,0 @@ Choose an existing secret from Secrets Manager.
-Create and use a new secret
@@ -31,6 +30,0 @@ Create and use a new secret
-ElastiCache will create a secret to store your specified credentials.
-
-None
-    
-
-Source doesn't require authentication.
@@ -42 +36 @@ The secret's contents depend on how your source authenticates.
-If your source authenticates users by name, store a user name and a password in the following format:
+If your source authenticates users by name, store a user name and a password in the following JSON format:
@@ -68 +62 @@ Where:
-The prepare step validates the secret's format, whether you created the secret or ElastiCache created it for you. An empty secret, a secret that is not valid JSON, a secret with no `password` field, or a user name or password that does not meet the requirements above each fail with a specific message. If your source password does not meet them, change it on your source before you prepare the migration.
+The prepare step validates the secret's format, whether you created the secret or ElastiCache created it for you. An empty secret, a secret that is not valid JSON, a secret with no `password` field, or a user name or password that does not meet the preceding requirements each fail with a specific message. If your source password does not meet them, change it on your source before you prepare the migration.
@@ -74 +68 @@ ElastiCache reads the secret with its own service credentials, so the secret nee
-The following permissions are required:
+The following permissions are required.
@@ -82 +76 @@ Your IAM identity | `secretsmanager:GetSecretValue`, `kms:Decrypt`, `ec2:Describ
-The following resource policy grants ElastiCache read access to the secret.
+The following resource policy grants ElastiCache read access to the secret:
@@ -99 +93 @@ If the secret is encrypted with a customer managed AWS KMS key, grant that servi
-Add the following statement to the key policy of the customer managed key that encrypts the secret.
+Add the following statement to the key policy of the customer managed key that encrypts the secret:
@@ -123 +117 @@ If your source uses a single password and no user names, ElastiCache connects wi
-If your source authenticates users by name and controls what each one can do, create a user for the migration and grant it the following permissions. Run this command against every node in your source, or use whatever mechanism your source has for applying access control across the cluster:
+If your source authenticates users by name and controls what each one can do, create a user for the migration and grant it the following permissions. Run this valkey-cli command against every node in your source, or use whatever mechanism your source has for applying access control across the cluster:
@@ -173 +167 @@ Pass the secret ARN in the source authentication configuration:
-        --customer-node-endpoint-list "Address='10.0.0.10',Port=6379" \
+        --customer-node-endpoint-list "Address='192.0.2.10',Port=6379" \
@@ -181 +175 @@ Where:
-  * `10.0.0.10` and `6379` are the private address and port of one node in your source cache. ElastiCache discovers the rest of your topology from this node.
+  * `192.0.2.10` and `6379` are the private address and port of one node in your source cache. ElastiCache discovers the rest of your topology from this node.
@@ -205 +199 @@ ElastiCache verifies that your source's server certificate chains to a CA certif
-        --customer-node-endpoint-list "Address='10.0.0.10',Port=6379" \
+        --customer-node-endpoint-list "Address='192.0.2.10',Port=6379" \
@@ -219,13 +212,0 @@ If your source accepts unencrypted connections, set `SourceTlsMode` to `none`. P
-## Related topics
-
-  * [Prerequisites for online migration to ElastiCache Serverless](./migration-to-serverless-prerequisites.html)
-
-  * [Online migration to ElastiCache Serverless](./migration-to-serverless.html)
-
-  * [Migrate your data to ElastiCache Serverless](./migration-to-serverless-procedure.html)
-
-  * [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html)
-
-
-
-
@@ -238 +219 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Prerequisites
+Prerequisites and limitations