AWS mgn documentation change
Summary
Rebranded 'Application Migration Service' to 'AWS Transform MGN' and 'MGN' throughout the document
Security assessment
Changes are purely branding updates with no security implications. No vulnerabilities, security features, or security configurations were modified or added. All security-related guidance (e.g., avoiding EC2-Classic, not adding security groups) remains unchanged.
Diff
diff --git a/mgn/latest/ug/key-considerations.md b/mgn/latest/ug/key-considerations.md index 6c839cc6f..888549de9 100644 --- a//mgn/latest/ug/key-considerations.md +++ b//mgn/latest/ug/key-considerations.md @@ -5 +5 @@ -[Documentation](/index.html)[Application Migration Service](/mgn/index.html)[User Guide](what-is-mgn.html) +[Documentation](/index.html)[AWS Transform MGN](/mgn/index.html)[User Guide](what-is-mgn.html) @@ -13 +13 @@ There are several key considerations when configuring your EC2 launch template. - 1. **Instance Type** – Ensure that you select an instance type that matches the hardware requirements of your source server. AWS Application Migration Service always utilizes the instance type that is set on the Amazon EC2 launch template unless the **Instance right-sizing** feature is activated. + 1. **Instance Type** – Ensure that you select an instance type that matches the hardware requirements of your source server. AWS Transform MGN always utilizes the instance type that is set on the Amazon EC2 launch template unless the **Instance right-sizing** feature is activated. @@ -17 +17 @@ There are several key considerations when configuring your EC2 launch template. - * If you change your instance type and do not deactivate the instance right-sizing feature, then AWS Application Migration Service uses the instance type determined by the **Instance right-sizing** feature and not the instance type you chose in the EC2 launch template. Application Migration Service verifies the instance type once per hour, as a result, if you did not deactivate the instance right-sizing feature, the first time instance launch may still utilize the instance type you set in the EC2 launch template, but any subsequent launches use the right-sizing instance. + * If you change your instance type and do not deactivate the instance right-sizing feature, then AWS Transform MGN uses the instance type determined by the **Instance right-sizing** feature and not the instance type you chose in the EC2 launch template. MGN verifies the instance type once per hour, as a result, if you did not deactivate the instance right-sizing feature, the first time instance launch may still utilize the instance type you set in the EC2 launch template, but any subsequent launches use the right-sizing instance. @@ -37 +37 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 7. **Networking platform** – AWS Application Migration Service only supports **Virtual Private Cloud (VPC)**. EC2-Classic is **not** supported. Do **not** add any security groups under the network platform. + 7. **Networking platform** – AWS Transform MGN only supports **Virtual Private Cloud (VPC)**. EC2-Classic is **not** supported. Do **not** add any security groups under the network platform. @@ -39 +39 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 8. **Custom device name** – Do not alter this field. AWS Application Migration Service uses the device name as defined on the source server in order to map disks on the test or cutover instance. You can use this field to identify your disks. + 8. **Custom device name** – Do not alter this field. AWS Transform MGN uses the device name as defined on the source server in order to map disks on the test or cutover instance. You can use this field to identify your disks. @@ -41 +41 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 9. **Disks** – You cannot add disks to the EC2 launch template. Any disks that are added that do not exist on the source machine are ignored by AWS Application Migration Service. + 9. **Disks** – You cannot add disks to the EC2 launch template. Any disks that are added that do not exist on the source machine are ignored by AWS Transform MGN. @@ -43 +43 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 10. **Launch template name** – Do not alter this field. AWS Application Migration Service automatically names this field. + 10. **Launch template name** – Do not alter this field. AWS Transform MGN automatically names this field. @@ -45 +45 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 11. **System tag** – Do not alter this field. Application Migration Service automatically adds system tags that match the EC2 launch template to the specific source server. You can recognize which source server the launch template is matched with by the **ID** field. + 11. **System tag** – Do not alter this field. MGN automatically adds system tags that match the EC2 launch template to the specific source server. You can recognize which source server the launch template is matched with by the **ID** field. @@ -47 +47 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 12. **Automatic cleanup** – Application Migration Service deletes the EC2 launch template and launch configuration for machines that have been disconnected from AWS Application Migration Service or machines for which the cutover has been finalized 90 minutes after disconnect or cutover finalization. This aids in ensuring that your account does not surpass the AWS 5000 EC2 launch template limit. + 12. **Automatic cleanup** – MGN deletes the EC2 launch template and launch configuration for machines that have been disconnected from AWS Transform MGN or machines for which the cutover has been finalized 90 minutes after disconnect or cutover finalization. This aids in ensuring that your account does not surpass the AWS 5000 EC2 launch template limit.