AWS AmazonElastiCache: Clarify subnet/AZ requirement for serverless migration
Summary
Clarifies that in Regions with only two Availability Zones (e.g., US West (N. California)) a subnet in each of the two AZs is sufficient for the target serverless cache.
Security assessment
The edit only relaxes a subnet-count prerequisite for two-AZ Regions; it concerns migration setup and availability, not network security controls or exposure.
Evidence
- * 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.
Diff
diff --git a/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md b/AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md index 4a3ef4a..ba39719 100644 --- a//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md +++ b//AmazonElastiCache/latest/dg/migration-to-serverless-prerequisites.md @@ -101 +101 @@ ElastiCache connects to your source from the VPC of your target cache. Confirm t - * 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. + * Create your target cache with at least three subnets in different Availability Zones, each with free IP addresses. In a Region where your account has two Availability Zones, such as US West (N. California), use a subnet in each of the two. 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.