AWS AmazonElastiCache: ElastiCache Serverless migration prerequisites: TLS, auth, network
Summary
Rewrites the online-migration prerequisites for ElastiCache Serverless: adds a 'Protected mode' source requirement, an 'Authentication' target requirement (same users/credentials as source), network reachability guidance (bind nodes to private IPs, allow inbound TCP from the target's security group/CIDR), a note that the migration endpoint requires TLS and that the target security group must allow 6379/6380, and clarifies subnet, ENI, and Secrets Manager secret retention requirements.
Security assessment
The added text documents security-relevant prerequisites rather than fixing a specific vulnerability: it states that the migration endpoint requires TLS (encryption in transit), that the target security group must permit inbound TCP on 6379/6380, that source nodes must bind to reachable private IPs with inbound access limited to the target's security group/CIDR, that a passwordless source must disable protected mode, and that target users/credentials must match the source. These are hardening/configuration guidance for a migration path, with no CVE or incident referenced, so it is security documentation of medium impact.
Evidence
+Your application connects to the migration endpoint with TLS, because all ElastiCache Serverless caches use encryption in transit. If your application reaches your source without TLS, turn on TLS in your client before you point it at the migration endpoint. The security group of your target cache must allow inbound TCP traffic from your application on ports 6379 and 6380, because many clients connect to both.
Diff
diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md b/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md index a727f61..c0d95ee 100644 --- a//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md +++ b//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md @@ -11 +11 @@ Source cache requirementsTarget cache requirementsNetwork requirementsCommand be -Before you start an online migration, confirm that your source cache and your target cache meet the following requirements. ElastiCache checks these requirements when you prepare the migration and checks some of them again when you start the data sync. If a requirement is not met, the step fails. ElastiCache reports a failure event on the cache that names the requirement. If the prepare step fails, the migration is rolled back, so the `Migration` object is removed and your cache returns to `available`. Correct the requirement, then try again. +Before you start an online migration, confirm that your source cache and your target cache meet the following requirements. ElastiCache checks these requirements when you prepare the migration and checks some of them again when you start the data sync. If a requirement is not met, the step fails. ElastiCache reports a failure event on the cache that names the requirement. If the prepare step fails, the migration is rolled back, so the `Migration` object, the record of your migration that `describe-serverless-caches` returns, is removed and your cache returns to `available`. Correct the requirement, then try again. @@ -27,0 +28 @@ Node health | Nodes must be healthy. ElastiCache checks node state when you prep +Protected mode | Protected mode turned off (`protected-mode no`) on a source that has no password. With protected mode on, a node without a password accepts only local connections, so ElastiCache cannot connect to it. A source that requires a password can keep protected mode on. | Prepare @@ -33 +34 @@ A second, separate check applies while the migration is running. If your source -**Key name size.** No key name in your source can exceed 4 KiB, which is the ElastiCache Serverless limit. An oversized key name fails the migration during the initial data load, and you cannot start the data sync again. ElastiCache writes the key to your target before it reports the failure. To try again, end the migration with force complete. Your migration endpoint then serves from your target, so move your application traffic back to your source. Then flush the target and prepare a new migration. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html). +**Key name size.** No key name in your source can exceed 4 KiB, which is the ElastiCache Serverless limit. An oversized key name fails the migration during the initial data load, and you cannot start the data sync again. ElastiCache writes the key to your target before it reports the failure. To try again, first point your application back at your source's own endpoint, and then end the migration with force complete, which switches the migration endpoint to your target. Then flush the target, remove or rename every key on your source whose name exceeds 4 KiB, and prepare a new migration. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html). @@ -56,0 +58 @@ Version | Runs Valkey 7.2, 8.1, or 9.0, at a version at least as high as your so +Authentication | Accepts the credentials that your application uses on your source. If your source requires authentication, set up the same users on your target before you prepare the migration. 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). @@ -71 +73 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t -Your target cache must have a subnet in each Availability Zone that ElastiCache Serverless uses in your AWS Region. If it does not, the prepare step fails. +Your source nodes must listen on addresses that this VPC can reach. The default Valkey and Redis OSS configuration file binds to `127.0.0.1`, which accepts only local connections, so bind each node to its private IP address. Each node must also report a reachable address in its cluster topology, because ElastiCache discovers the rest of your nodes from the first one. For the security group rule, allow inbound TCP traffic on your source port from the security group of your target cache, or from the IPv4 CIDR ranges of its subnets. @@ -73 +75 @@ Your target cache must have a subnet in each Availability Zone that ElastiCache -Preparing a migration creates network interfaces and a security group in your account, so you need quota headroom in four places. The prepare step fails if any of them is exhausted: +Create your target cache with at least three subnets in different Availability Zones, each with free IP addresses. You cannot change the subnets of a serverless cache after you create it. If the prepare step or the data sync fails on subnets, the error message names the Availability Zones that need a subnet. @@ -75 +77 @@ Preparing a migration creates network interfaces and a security group in your ac - * Free IP addresses in the subnets your target cache uses. +Preparing a migration creates network interfaces in the subnets of your target cache. They use the security groups of your target cache, and ElastiCache deletes them when the migration completes. The prepare step fails if your target's subnets have no free IP addresses or your VPC has no network interface quota headroom. @@ -77,10 +79 @@ Preparing a migration creates network interfaces and a security group in your ac - * Network interface quota for the VPC. - - * Security group quota for the VPC. - - * Security group rule quota. - - - - -**Resources that prepare creates.** Do not delete the resources that prepare creates. The security group that ElastiCache creates when you prepare the migration, and the Secrets Manager secret you provided, both must keep existing until the migration completes. If a node is replaced during the migration, ElastiCache re-runs network and authentication setup. A missing security group or secret fails that step. +**Resources to keep.** Keep the Secrets Manager secret that you provided until the migration completes. If a node is replaced during the migration, ElastiCache runs network and authentication setup again, and a missing secret fails that step. @@ -103,0 +97,2 @@ Some commands behave differently on ElastiCache Serverless than on a self-manage +Your application connects to the migration endpoint with TLS, because all ElastiCache Serverless caches use encryption in transit. If your application reaches your source without TLS, turn on TLS in your client before you point it at the migration endpoint. The security group of your target cache must allow inbound TCP traffic from your application on ports 6379 and 6380, because many clients connect to both. + @@ -140 +135 @@ The ElastiCache Service Level Agreement applies to your ElastiCache Serverless c -**Pipelining is not supported during the migration.** If your application pipelines commands, they are serialized during the migration. A batch of 100 commands then takes 100 round trips instead of one. Latency for those batches increases in proportion to the batch depth. +**Pipelining is not supported during the migration.** If your application pipelines commands, the migration endpoint serializes them from the moment the migration reads `ready-to-sync`. A batch of 100 commands then takes 100 round trips instead of one. Latency for those batches increases in proportion to the batch depth.