AWS transform documentation change
Summary
Added section on existing VPC detection during network migration and CIDR conflict resolution recommendations.
Security assessment
Documentation change describes operational improvements for network visibility and conflict prevention. No security vulnerabilities, exploits, or security-specific features are mentioned.
Diff
diff --git a/transform/latest/userguide/transform-vmware-migrate-network.md b/transform/latest/userguide/transform-vmware-migrate-network.md index 03144d435..d45ba8b92 100644 --- a//transform/latest/userguide/transform-vmware-migrate-network.md +++ b//transform/latest/userguide/transform-vmware-migrate-network.md @@ -258,0 +259,10 @@ After AWS Transform generates your target network configuration, you can review +### Existing VPCs in your target account + +If your target account already contains VPCs — from previous migration phases or parallel infrastructure projects — AWS Transform automatically detects them and displays them alongside your mapped VPCs during the review process. For multi-account migrations, AWS Transform detects existing VPCs across all accounts in your AWS Organization. + +This visibility helps you understand how your planned network relates to your existing infrastructure, identify potential CIDR conflicts, and make informed decisions before deployment. + +###### Note + +AWS Transform detects existing VPCs only (not subnets or other resources). Detection is read-only — AWS Transform does not modify your existing VPCs. + @@ -348,0 +359,2 @@ AWS Transform might recommend the following optimizations: + * **CIDR conflict resolution:** Flags overlapping CIDR ranges between your mapped VPCs and existing VPCs across all accounts in your AWS Organization. Conflicting VPCs are shown first. You can resolve conflicts by re-addressing the mapped VPC, excluding or deleting it, or acknowledging the conflict and resolving it yourself after deployment. +