AWS Security ChangesHomeSearch

AWS AmazonElastiCache: Restructure serverless migration prerequisites; add supported sources

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

File: AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md · Type: network

Summary

Reorganizes the online migration prerequisites page: tables are converted to bullet lists, sections are reordered, a new 'Supported sources and targets' section is added (self-managed Valkey 7.2-8.1 / Redis OSS 4.0-7.2 in cluster mode to ElastiCache Serverless for Valkey), troubleshooting and related-topics content is removed (moved to other pages), and internal links are retargeted. Security-relevant guidance on private networking, no public endpoint, TLS, and Secrets Manager secret retention is preserved.

Security assessment

The diff is a documentation reorganization (tables to bullets, section reordering, link retargeting) with no reference to a CVE, incident, or fixed vulnerability, so it is not security-issue-related. However, it does document security features and best practices: target caches must have no public endpoint, sources must be reachable only via private endpoints with restrictive security-group rules, TLS is required because all serverless caches encrypt in transit, and the Secrets Manager secret must remain valid for the migration. These are hardening/exposure-prevention guidance, so it adds security documentation at medium severity.

Evidence

  * **No public endpoint** – The cache has no public endpoint. Leave public connectivity turned off when you create the target cache. For a cache that already exists, confirm that it has no public endpoint before you prepare the migration.

Diff

diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md b/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md
index 01289a9..4a3ef4a 100644
--- a//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md
+++ b//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md
@@ -7 +7 @@
-Source cache requirementsTarget cache requirementsNetwork requirementsCommand behavior during a migrationClient configurationWhat ElastiCache manages and what you manageLimitationsTroubleshooting a failed prepare stepIf a key name exceeds 4 KiBRelated topics
+Supported sources and targetsSource cache requirementsTarget cache requirementsNetwork requirementsCommand behavior during a migrationClient configurationLimitations
@@ -9 +9 @@ Source cache requirementsTarget cache requirementsNetwork requirementsCommand be
-# Prerequisites for online migration to ElastiCache Serverless
+# Prerequisites and limitations for online migration to ElastiCache Serverless
@@ -12,0 +13,15 @@ Before you start an online migration, confirm that your source cache and your ta
+## Supported sources and targets
+
+Online migration supports the following source and target combinations:
+
+  * **Source** – Self-managed Valkey 7.2 through 8.1, or Redis OSS 4.0 through 7.2, running on Amazon EC2 in cluster mode.
+
+  * **Target** – An ElastiCache Serverless for Valkey cache running Valkey 7.2, 8.1, or 9.0, that you create before you start.
+
+
+
+
+Your source version must be no higher than your target version. ElastiCache managed caches and Amazon MemoryDB caches are not supported as sources. Valkey 9.0 is supported as a target but not as a source.
+
+Your source must run in cluster mode. To migrate a source that runs with cluster mode disabled, use online migration to a node-based cluster. For more information, see [Online migration to ElastiCache node-based clusters](./OnlineMigration.html).
+
@@ -30,2 +45,2 @@ Replication commands | Your source must accept a replica connection from the mig
-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 recover, see If a key name exceeds 4 KiB. | During the initial data load  
-CPU headroom on source primaries | Your source primaries serve your application's traffic for the whole migration, up until cutover. You need CPU headroom on your source primaries to serve your full read and write workload while the migration runs. Review your workload and scale out before you prepare the migration. A source primary that becomes overloaded can compromise the health of the migration. For more information about when traffic moves off your source, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html). | Not checked. Your responsibility.  
+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 recover, see [Troubleshooting a key name that exceeds 4 KiB](./migration-to-serverless-troubleshooting.html#migration-to-serverless-troubleshooting-key-name-size). | During the initial data load  
+CPU headroom on source primaries | Your source primaries serve your application's traffic for the whole migration, up until cutover. You need CPU headroom on your source primaries to serve your full read and write workload while the migration runs. Review your workload and scale out before you prepare the migration. A source primary that becomes overloaded can compromise the health of the migration. For more information about when traffic moves off your source, see [Cutting over](./migration-to-serverless-procedure.html#migration-to-serverless-complete). | Not checked. Your responsibility.  
@@ -33 +48 @@ Memory for the initial full sync | ElastiCache replicates your data with the rep
-Stable environment | Your environment must stay stable for the whole migration. Three things must stay valid until the migration completes: your network path, your source TLS certificate, and your AWS Secrets Manager credentials. If any of them changes mid-migration, ElastiCache reports a migration error event, and the migration cannot be started again. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html). | During the migration  
+Stable environment | Your environment must stay stable for the whole migration. Three things must stay valid until the migration completes: your network path, your source TLS certificate, and your AWS Secrets Manager credentials. If any of them changes mid-migration, ElastiCache reports a migration error event, and the migration cannot be started again. For more information, see [Cutting over](./migration-to-serverless-procedure.html#migration-to-serverless-complete). | During the migration  
@@ -42 +57 @@ A second, separate check applies while the migration is running. If your source
-Create an ElastiCache Serverless for Valkey cache before you start. Your target must meet all of the following requirements.
+Create an ElastiCache Serverless for Valkey cache before you start. Your target must meet all of the following requirements:
@@ -44,9 +59 @@ Create an ElastiCache Serverless for Valkey cache before you start. Your target
-Requirement | What your target cache must meet  
----|---  
-Available and idle | In the `available` state with no other operation in progress.  
-Empty | Contains no keys. Flush the target yourself before you prepare the migration. If the target contains data, preparation fails.  
-No active pub/sub connections | No subscribed clients when you prepare the migration.  
-No public endpoint | No public endpoint. Leave public connectivity turned off when you create the target cache. For a cache that already exists, confirm that it has no public endpoint before you prepare the migration.  
-Network type | IPv4. ElastiCache rejects a target cache that uses the IPv6 or dual-stack network type.  
-Version | Runs Valkey 7.2, 8.1, or 9.0, at a version at least as high as your source version.  
-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).  
+  * **Available and idle** – The cache is in the `available` state with no other operation in progress.
@@ -54 +61 @@ Authentication | Accepts the credentials that your application uses on your sour
-Your target inherits the standard ElastiCache Serverless limits, and your data must fit inside them:
+  * **Empty** – The cache contains no keys. Flush the target yourself before you prepare the migration. If the target contains data, preparation fails.
@@ -56,6 +63 @@ Your target inherits the standard ElastiCache Serverless limits, and your data m
-Limit | Value  
----|---  
-Size per cache | 5,000 GiB  
-Size per slot | 32 GiB  
-ElastiCache processing units | 15,000,000 ECPUs per second  
-Key name length | 4 KiB  
+  * **No active pub/sub connections** – The cache has no subscribed clients when you prepare the migration.
@@ -63 +65 @@ Key name length | 4 KiB
-## Network requirements
+  * **No public endpoint** – The cache has no public endpoint. Leave public connectivity turned off when you create the target cache. For a cache that already exists, confirm that it has no public endpoint before you prepare the migration.
@@ -65 +67 @@ Key name length | 4 KiB
-ElastiCache connects to your source from the VPC of your target cache. Confirm the following:
+  * **Network type** – The cache uses the IPv4 network type. ElastiCache rejects a target cache that uses the IPv6 or dual-stack network type.
@@ -67 +69 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  1. Confirm that your source is reachable on a private endpoint from that VPC. Also confirm that your source security group allows inbound traffic from ElastiCache.
+  * **Version** – The cache runs Valkey 7.2, 8.1, or 9.0, at a version at least as high as your source version.
@@ -69 +71 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  2. 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.
+  * **Authentication** – The cache 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 +72,0 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  3. 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 +73,0 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  4. 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.
@@ -75 +74,0 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  5. 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. Because you cannot change the subnets of a serverless cache, create a new target cache with a subnet in each Availability Zone that the message names, and prepare the migration again.
@@ -77 +76 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  6. 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.
+Your target inherits the standard ElastiCache Serverless limits, and your data must fit inside them:
@@ -79 +78 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-  7. 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.
+  * **Size per cache** – 5,000 GiB
@@ -80,0 +80 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
+  * **Size per slot** – 32 GiB
@@ -81,0 +82 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
+  * **ElastiCache processing units** – 15,000,000 ECPUs per second
@@ -82,0 +84 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
+  * **Key name length** – 4 KiB
@@ -84 +85,0 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-## Command behavior during a migration
@@ -86 +86,0 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t
-While your application is served through the migration endpoint, ElastiCache Serverless command support applies, not your source's command support.
@@ -88 +87,0 @@ While your application is served through the migration endpoint, ElastiCache Ser
-Commands that ElastiCache Serverless does not support are rejected at the migration endpoint, the same as they would be on any serverless cache.
@@ -90 +89 @@ Commands that ElastiCache Serverless does not support are rejected at the migrat
-Some commands behave differently on ElastiCache Serverless than on a self-managed cache. These include `FLUSH`, the `CLUSTER` commands, and the publish and subscribe commands. ElastiCache Serverless requires every Lua script call to declare at least one key. A call such as `EVALSHA` with zero keys returns `ERR Lua scripts without any input keys are not supported`. Review your application's use of these commands before you start. For more information, see [Supported and restricted Valkey, Memcached, and Redis OSS commands](./SupportedCommands.html).
+## Network requirements
@@ -92 +91 @@ Some commands behave differently on ElastiCache Serverless than on a self-manage
-Writes during the migration
+ElastiCache connects to your source from the VPC of your target cache. Confirm the following:
@@ -94 +93 @@ Writes during the migration
-Do not send writes directly to your source during the migration. Commands that ElastiCache Serverless does not support are not replicated. A client can bypass the migration endpoint and write an unsupported command straight to your source. That makes your target diverge. ElastiCache reports a migration error event when it detects this. After ElastiCache reports that error, you cannot start the migration again. To end it, you complete the migration with force, which accepts the inconsistency.
+  * Confirm that your source is reachable on a private endpoint from that VPC. Also confirm that your source security group allows inbound traffic from ElastiCache.
@@ -96 +95 @@ Do not send writes directly to your source during the migration. Commands that E
-The following commands need your attention during a migration:
+  * 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.
@@ -98,4 +97 @@ The following commands need your attention during a migration:
-What | What to do  
----|---  
-Scripts | Scripts you loaded on your source before the migration are not replicated to your target. Re-issue `SCRIPT LOAD` for them through the migration endpoint any time after the migration reaches `ready-to-sync` and before cutover. A script that is missing on the target returns `NOSCRIPT` after cutover.  
-Pub/sub subscriptions | Pub/sub subscriptions do not survive cutover. Subscribed clients are disconnected at cutover and have to reconnect and re-subscribe.  
+  * 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.
@@ -103 +99 @@ Pub/sub subscriptions | Pub/sub subscriptions do not survive cutover. Subscribed
-## Client configuration
+  * 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.
@@ -105 +101 @@ Pub/sub subscriptions | Pub/sub subscriptions do not survive cutover. Subscribed
-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.
+  * 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. Because you cannot change the subnets of a serverless cache, create a new target cache with a subnet in each Availability Zone that the message names, and prepare the migration again.
@@ -107 +103 @@ Your application connects to the migration endpoint with TLS, because all Elasti
-Instead of caching node IP addresses in your application, use the migration endpoint.
+  * 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.
@@ -109 +105 @@ Instead of caching node IP addresses in your application, use the migration endp
-Stay within Valkey's default limit of 10,000 client connections during a migration. If your workload needs more connections than that, open them gradually rather than all at once.
+  * 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.
@@ -111 +106,0 @@ Stay within Valkey's default limit of 10,000 client connections during a migrati
-Because commands are serialized during a migration, a client that relies on pipelining needs more concurrent connections to sustain the same request rate. If your client uses a connection pool, review its size before you migrate, and consider raising it for the duration of the migration. For more information about serialized commands, see the pipelining limitation in the Limitations section of this topic.
@@ -113 +107,0 @@ Because commands are serialized during a migration, a client that relies on pipe
-## What ElastiCache manages and what you manage
@@ -115 +108,0 @@ Because commands are serialized during a migration, a client that relies on pipe
-A migration spans your infrastructure and ours.
@@ -117,5 +110 @@ A migration spans your infrastructure and ours.
-ElastiCache manages | You manage  
----|---  
-The migration endpoint that your application connects to. | Your source cache, including its capacity, its engine version, and its availability. ElastiCache reads from your source but does not operate it.  
-The infrastructure that reads from your source cache and replicates to your target during the migration. | The source requirements on this page, including replication support, the memory limit per node, the engine version range, and network reachability.  
-The target ElastiCache Serverless cache. | Your client configuration, including retry behavior, connection pooling, and not caching node IP addresses.  
+## Command behavior during a migration
@@ -123 +112 @@ The target ElastiCache Serverless cache. | Your client configuration, including
-A failed request can originate on either side. If you see errors during a migration, check your source cache health and capacity first. A source that is unavailable or out of memory surfaces as errors through the migration endpoint.
+While your application is served through the migration endpoint, ElastiCache Serverless command support applies, not your source's command support.
@@ -125 +114 @@ A failed request can originate on either side. If you see errors during a migrat
-The ElastiCache Service Level Agreement applies to your ElastiCache Serverless cache during a migration on the same terms as at any other time.
+Commands that ElastiCache Serverless does not support are rejected at the migration endpoint, the same as they would be on any serverless cache.
@@ -127 +116 @@ The ElastiCache Service Level Agreement applies to your ElastiCache Serverless c
-## Limitations
+Some commands behave differently on ElastiCache Serverless than on a self-managed cache. These include `FLUSH`, the `CLUSTER` commands, and the publish and subscribe commands. ElastiCache Serverless requires every Lua script call to declare at least one key. A call such as `EVALSHA` with zero keys returns `ERR Lua scripts without any input keys are not supported`. Review your application's use of these commands before you start. For more information, see [Supported and restricted Valkey, Memcached, and Redis OSS commands](./SupportedCommands.html).
@@ -129 +118 @@ The ElastiCache Service Level Agreement applies to your ElastiCache Serverless c
-The following limitations apply during a migration:
+Writes during the migration
@@ -131,12 +120 @@ The following limitations apply during a migration:
-Limitation | What to do  
----|---  
-Permanent errors | Migration errors are reported as permanent. A migration that has reported an error cannot be started again, even after you fix the underlying problem. You can stop it, and your only way to end it is to complete the migration with force. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).  
-Force complete | Force complete does not roll back. It skips the pre-cutover health check and the cluster-wide convergence check. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).  
-Rollback after cutover | There is no rollback after cutover. To return to your source cache, you must move your application traffic back to it yourself. Writes that your application makes after cutover exist only on your target. For more information, see [Cutover modes for online migration to ElastiCache Serverless](./migration-to-serverless-cutover.html).  
-The reader endpoint is not supported during a migration | Send your traffic to the migration endpoint and not the cache's reader endpoint.  
-One migration per cache | A cache can be the target of only one migration at a time.  
-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.  
-RESP3 Pub/Sub with regular commands on the same connection | RESP3 lets a client run regular commands on a connection that has active Pub/Sub subscriptions (`SUBSCRIBE` or `SSUBSCRIBE`). This isn't supported while a migration is in progress. During migration, use separate connections for Pub/Sub and for regular commands. Most client libraries do this by default. This restriction ends when the migration completes.  
-Total migration throughput scales with your source shard count | A source with many shards migrates faster than a source with few.  
-High-throughput sources with few shards | This release is not suited to a high-throughput source with few shards. Migration throughput is provisioned per source shard. A source that concentrates high traffic into a small number of shards is most likely to be limited. If that describes your source, review the CPU headroom on source primaries prerequisite in the source cache requirements, or plan the migration for a lower-traffic period.  
-Billing after you stop the data sync | Billing does not stop when you stop the data sync. `StopMigration` leaves the migration infrastructure provisioned. `CompleteMigration` is the call that ends the migration and its charges. Your target ElastiCache Serverless cache continues to bill until you delete it.  
+Do not send writes directly to your source during the migration. Commands that ElastiCache Serverless does not support are not replicated. A client can bypass the migration endpoint and write an unsupported command straight to your source. That makes your target diverge. ElastiCache reports a migration error event when it detects this. After ElastiCache reports that error, you cannot start the migration again. To end it, you complete the migration with force, which accepts the inconsistency.
@@ -144 +122 @@ Billing after you stop the data sync | Billing does not stop when you stop the d
-## Troubleshooting a failed prepare step
+The following commands need your attention during a migration:
@@ -146 +124 @@ Billing after you stop the data sync | Billing does not stop when you stop the d
-When the prepare step fails, the target cache's Events tab shows the reason. The following table lists the reasons and what to check.
+  * **Scripts** – Scripts you loaded on your source before the migration are not replicated to your target. Re-issue `SCRIPT LOAD` for them through the migration endpoint any time after the migration reaches `ready-to-sync` and before cutover. A script that is missing on the target returns `NOSCRIPT` after cutover.
@@ -148,5 +126 @@ When the prepare step fails, the target cache's Events tab shows the reason. The
-Reason in the event | What to check  
----|---  
-"The serverless cache must have no keys before migration can begin." | Your target contains data. Run `FLUSHALL` on the target before you prepare the migration, or choose an empty cache.  
-"The serverless cache is not yet ready for migration. Please try again later." | Wait, and then prepare the migration again.  
-"Unable to connect to source cluster." |  This reason covers several causes. Check each of the following:
+  * **Pub/sub subscriptions** – Pub/sub subscriptions do not survive cutover. Subscribed clients are disconnected at cutover and have to reconnect and re-subscribe.
@@ -154,5 +127,0 @@ Reason in the event | What to check
-  * The source security group allows inbound TCP on the source port from the target cache's security group or subnets.
-  * Each source node binds to its private IP address and reports a reachable address in its cluster topology.
-  * The source address is a private IP address or a host name that resolves through public DNS.
-  * Protected mode is off on a source that has no password.
-  * The migration user has every permission in [Permissions for the migration user](./migration-to-serverless-auth.html#migration-to-serverless-auth-permissions).
@@ -161,3 +129,0 @@ Reason in the event | What to check
-An access denied message for the secret | The secret's resource policy grants `secretsmanager:GetSecretValue` to `elasticache.amazonaws.com`, the key policy grants `kms:Decrypt`, neither statement has an `aws:SourceAccount` or `aws:SourceArn` condition, and your IAM identity has `secretsmanager:GetSecretValue`, `kms:Decrypt` and `ec2:DescribeSubnets`.  
-A subnet message that names Availability Zones | Create a new target cache with a subnet in each Availability Zone that the message names, and prepare the migration again.  
-A failure after you provide TLS settings | Provide the PEM-encoded CA certificates with `verify-ca`. The event might not name the certificate authority.  
@@ -165 +131 @@ A failure after you provide TLS settings | Provide the PEM-encoded CA certificat
-## If a key name exceeds 4 KiB
+## Client configuration
@@ -167 +133 @@ A failure after you provide TLS settings | Provide the PEM-encoded CA certificat
-An oversized key name fails the migration during the initial data load. Recover as follows:
+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.
@@ -169 +135 @@ An oversized key name fails the migration during the initial data load. Recover
-  1. Point your application back at your source's own endpoint.
+Instead of caching node IP addresses in your application, use the migration endpoint.
@@ -171 +137 @@ An oversized key name fails the migration during the initial data load. Recover
-  2. End the migration with force complete, which switches the migration endpoint to your target.
+Stay within Valkey's default limit of 10,000 client connections during a migration. If your workload needs more connections than that, open them gradually rather than all at once.
@@ -173 +139 @@ An oversized key name fails the migration during the initial data load. Recover