AWS mgn documentation change
Summary
Clarified private IP usage constraints and added subnet conflict warnings
Security assessment
Changes address operational network configuration issues (IP conflicts) rather than security vulnerabilities. No evidence of security exploit mitigation.
Diff
diff --git a/mgn/latest/ug/copy-private.md b/mgn/latest/ug/copy-private.md index 5958cf44d..9048ea1fc 100644 --- a//mgn/latest/ug/copy-private.md +++ b//mgn/latest/ug/copy-private.md @@ -9 +9 @@ Choose whether you want AWS Application Migration Service to ensure that the pri -AWS Application Migration Service (AWS MGN) will monitor the source server on an hourly basis to identify the private IP. AWS MGN will use the private IP of the primary network interface. +AWS Application Migration Service (AWS MGN) monitors the source server on an hourly basis to identify the private IP. AWS MGN uses the private IP of the primary network interface. @@ -13 +13 @@ The **No** option is chosen by default. Click **No** if you do not want the priv -Click **Yes** if you want to use a private IP. The IP will be shown in brackets next to the option. +Click **Yes** if you want to use a private IP. The IP is shown in brackets next to the option. @@ -17 +17,6 @@ Click **Yes** if you want to use a private IP. The IP will be shown in brackets -If you clicked **Yes** , ensure that the IP range of the subnet you set in the EC2 launch template includes the private IP address. + * Removing a private IP from a specific server's settings does not remove it from the launch template. + + * If you chose **Yes** , ensure that the IP range of the subnet you set in the EC2 launch template includes the private IP address. + + * If the both the source server and the test or cutover instance shares the same subnet though a VPN, then the source private IP is already in use, and the **Copy private IP** option should not be used. + @@ -19 +23,0 @@ If you clicked **Yes** , ensure that the IP range of the subnet you set in the E -###### Note @@ -21 +24,0 @@ If you clicked **Yes** , ensure that the IP range of the subnet you set in the E -If the both the source server and the test or cutover instance shares the same subnet though a VPN, then the source private IP is already in use, and the **Copy private IP** option should not be used.