AWS Security ChangesHomeSearch

AWS transform documentation change

Service: transform · 2025-07-04 · Documentation low

File: transform/latest/userguide/transform-vmware-migrate-network.md

Summary

Updated terminology from 'on-premises-network' to 'source network' and clarified tool usage context

Security assessment

The changes are terminology updates (e.g., 'on-premises' to 'source') and do not address security vulnerabilities or introduce new security features. The existing note about security group limitations with RVTools remains unchanged.

Diff

diff --git a/transform/latest/userguide/transform-vmware-migrate-network.md b/transform/latest/userguide/transform-vmware-migrate-network.md
index 0aa87061a..435f433fd 100644
--- a//transform/latest/userguide/transform-vmware-migrate-network.md
+++ b//transform/latest/userguide/transform-vmware-migrate-network.md
@@ -9 +9 @@ Generate VPC configurationTag network resourcesSecurity group association
-AWS Transform can migrate your VMware networks to AWS. You can use [RVTools](https://www.robware.net/) or [Import/Export for NSX](https://github.com/awslabs/import-export-for-nsx/) to capture on-premises-network data, and then import that data. The choice of tool depends on the type of on-premises network that you have. If you have an NSX-defined network, upload an NSX configuration file imported using the Import/Export for NSX tool. If you have a VSphere-constructs-defined network, you can upload an [RVTools](https://www.robware.net/) file. AWS Transform will use that data to generate Amazon VPC configurations for you to review and deploy in your target AWS account. If you upload an [RVTools](https://www.robware.net/) file, AWS Transform won't create security groups because **RVTools** files don't include the information required to generate security groups.
+AWS Transform can migrate your VMware networks to AWS. You can use [RVTools](https://www.robware.net/) or [Import/Export for NSX](https://github.com/awslabs/import-export-for-nsx/) to capture source network data, and then import that data. The choice of tool depends on the type of source network that you have. If you have an NSX-defined network, upload an NSX configuration file imported using the Import/Export for NSX tool. If you have a VSphere-constructs-defined network, you can upload an [RVTools](https://www.robware.net/) file. AWS Transform will use that data to generate Amazon VPC configurations for you to review and deploy in your target AWS account. If you upload an [RVTools](https://www.robware.net/) file, AWS Transform won't create security groups because **RVTools** files don't include the information required to generate security groups.
@@ -59 +59 @@ For both topologies AWS Transform doesn’t open the communication to the intern
-AWS Transform then analyzes your on-premises network data and translates your on-premises network to the following AWS networking resources as needed: VPCs, subnets, security groups, network access control lists (NACLs), NAT gateways, transit gateways, internet gateways, elastic IPs, routes, and route tables. AWS Transform then creates AWS CloudFormation templates and AWS Cloud Development Kit (AWS CDK) templates. Review the generated network configuration, and then either deploy it on your own or ask AWS Transform to deploy it for you. However, if you make changes to the generated configuration, you have to deploy the modified configuration yourself. If you choose to let AWS Transform deploy the network for you, it will also use tools such as Reachability Analyzer to run an analysis in order to check connectivity between subnets across multiple VPCs and under the same VPC.
+AWS Transform then analyzes your source network data and translates your source network to the following AWS networking resources as needed: VPCs, subnets, security groups, network access control lists (NACLs), NAT gateways, transit gateways, internet gateways, elastic IPs, routes, and route tables. AWS Transform then creates AWS CloudFormation templates and AWS Cloud Development Kit (AWS CDK) templates. Review the generated network configuration, and then either deploy it on your own or ask AWS Transform to deploy it for you. However, if you make changes to the generated configuration, you have to deploy the modified configuration yourself. If you choose to let AWS Transform deploy the network for you, it will also use tools such as Reachability Analyzer to run an analysis in order to check connectivity between subnets across multiple VPCs and under the same VPC.