AWS transform documentation change
Summary
Restructured network configuration documentation, reduced IP strategies from three to two options, and clarified combination possibilities
Security assessment
The changes reorganize network migration documentation without introducing new security controls or addressing security vulnerabilities. Mentions of security groups and IP-based access control reflect existing features rather than new security content.
Diff
diff --git a/transform/latest/userguide/transform-vmware-migrate-network.md b/transform/latest/userguide/transform-vmware-migrate-network.md index 07b7e2abf..b9d089108 100644 --- a//transform/latest/userguide/transform-vmware-migrate-network.md +++ b//transform/latest/userguide/transform-vmware-migrate-network.md @@ -123 +123 @@ If you want fine-grained control over the communication between the VPCs, choose -AWS Transform offers three IP addressing strategies for your migration: +The system offers two key network configuration choices for your migration @@ -125 +125 @@ AWS Transform offers three IP addressing strategies for your migration: - * **IP Address Retention:** Keep original IP addresses during migration. Ideal for lift-and-shift scenarios with legacy applications that have hard-coded IP dependencies or existing firewall rules. +**Network range selection:** @@ -127 +127 @@ AWS Transform offers three IP addressing strategies for your migration: - * **Static IP Assignment:** You can modify VPC CIDR ranges during migration, and AWS Transform automatically propagates changes to subnets, route tables, and security groups, and then assigns static IPs based on the CIDR. This is best for applications requiring predictable network behavior, DNS management, or IP-based access control. IPs persist across instance restarts using Elastic Network Interfaces (ENIs). + * **Keep Existing Ranges (IP Address Ranges Retention):** Keep original IP address ranges during migration. Ideal for lift-and-shift scenarios with legacy applications that have hard-coded IP dependencies or existing firewall rules. @@ -129 +129 @@ AWS Transform offers three IP addressing strategies for your migration: - * **Dynamic IP Assignment (AWS DHCP):** Automatically assign IPs from subnet pools at instance launch. Optimal for cloud-native applications, auto-scaling workloads, and container orchestration (ECS, EKS, ASGs). Reduces operational overhead but requires applications to use DNS or service discovery. + * **Update to new IP ranges (CIDR update):** You can modify each VPC CIDR range during migration, and AWS Transform automatically propagates changes to subnets, route tables, and security groups. @@ -133,0 +134,11 @@ AWS Transform offers three IP addressing strategies for your migration: +**IP addresses assignment:** + + * **Fixed IP addresses (Static):** the system assigns static IPs based on the CIDR. This is best for applications requiring predictable network behavior, DNS management, or IP-based access control. IPs persist across instance restarts using Elastic Network Interfaces (ENIs). + + * **Dynamic IP assignment (AWS DHCP):** Automatically assign IPs from subnet pools at instance launch. Optimal for cloud-native applications and auto-scaling workloads. Reduces operational overhead but requires applications to use DNS or service discovery. + + + + +You can combine either range selection with either IP assignment method. +