AWS transform documentation change
Summary
Added detailed subnet tagging requirements and expanded migration wave preparation steps
Security assessment
The changes introduce network configuration requirements (subnet tagging) that help ensure proper resource isolation and access control. While this relates to security best practices, there's no evidence of addressing a specific security vulnerability.
Diff
diff --git a/transform/latest/userguide/transform-vmware-migrate-waves.md b/transform/latest/userguide/transform-vmware-migrate-waves.md index eb1fc5f92..4688c09bb 100644 --- a//transform/latest/userguide/transform-vmware-migrate-waves.md +++ b//transform/latest/userguide/transform-vmware-migrate-waves.md @@ -5 +5,3 @@ -# Migrate waves +Prepare wavesMigrate waves + +# Prepare and migrate waves @@ -8,0 +11,4 @@ At this stage, you will see migration waves in the **Job Plan** pane. For each w +## Prepare waves + +Each wave includes a **Set up migration wave** task. On its **Collaboration** tab you can configure the wave's settings. + @@ -13 +19,11 @@ At this stage, you will see migration waves in the **Job Plan** pane. For each w - 2. In the **Job Plan** pane, choose **Confirm inventory for`wave-name`**. Download the inventory file and review the list of servers and Amazon EC2 configurations. Modify the file if necessary, but do not add or remove columns or change the titles of the existing columns. After you choose whether to continue with the file you downloaded or to upload a version of the file that you updated, choose **Continue**. + 2. In the **Staging area subnet** section, you can choose a staging area subnet from the dropdown menu of the available subnets. + +The list of subnets is obtained from Application Migration Service. Only VPC subnets that are tagged in Application Migration Service with appear in this list. To tag your subnets: + + 1. In the AWS console, open **VPC**. + + 2. Select a VPC. + + 3. Choose a subnet from the VPC. + + 4. In the subnet, select the **Tags** tab. @@ -15 +31,11 @@ At this stage, you will see migration waves in the **Job Plan** pane. For each w - 3. For each wave, choose your [IP assigment approach](https://docs.aws.amazon.com/AWSQT/flexible_ip/transform-vmware-migrate-network.html#vmware-migration-ip): + 5. Select the **Add new tag**. + + 6. Tag with the following key-value pairs. + +Key: `CreatedFor` Value: `AWSTransform` + +Key: `ATWorkspace` Value: ``workspace ID`` + + 3. In the **Job Plan** pane, choose **Confirm inventory for`wave-name`**. Download the inventory file and review the list of servers and Amazon EC2 configurations. Modify the file if necessary, but do not add or remove columns or change the titles of the existing columns. After you choose whether to continue with the file you downloaded or to upload a version of the file that you updated, choose **Continue**. + + 4. For each wave, choose your [IP assigment approach](https://docs.aws.amazon.com/AWSQT/flexible_ip/transform-vmware-migrate-network.html#vmware-migration-ip): @@ -27,0 +54,2 @@ AWS Transform provides Amazon EC2 recommendations based on the utilization speci +## Migrate waves + @@ -135 +163 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Prepare waves +Set up service permissions