AWS mgn documentation change
Summary
Renamed 'AWS Application Migration Service' to 'AWS Transform MGN' throughout the document and replaced full service name with 'MGN' abbreviation in multiple sections.
Security assessment
Changes are purely branding/nomenclature updates without any security implications. No vulnerabilities, security features, or security-related configurations were added or modified. The content about IP copying, tags, and boot modes remains unchanged in substance.
Diff
diff --git a/mgn/latest/ug/launch-template.md b/mgn/latest/ug/launch-template.md index 4178743fa..7233f1bcb 100644 --- a//mgn/latest/ug/launch-template.md +++ b//mgn/latest/ug/launch-template.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 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -The **Launch template** allows you to control the way AWS Application Migration Service launches instances in AWS. The default configuration defined in the template is automatically applied to every newly added server. +The **Launch template** allows you to control the way AWS Transform MGN launches instances in AWS. The default configuration defined in the template is automatically applied to every newly added server. @@ -45 +45 @@ In the **General launch settings** section, you can define: - * **Instance type right sizing** : If you select this option, AWS Application Migration Service launches a test or cutover AWS instance type that best matches the OS, CPU, and RAM of your source server. Please note that the AWS instance type selected by Application Migration Service when this option is selected overwrites the instance type defined in your EC2 launch template. + * **Instance type right sizing** : If you select this option, AWS Transform MGN launches a test or cutover AWS instance type that best matches the OS, CPU, and RAM of your source server. Please note that the AWS instance type selected by MGN when this option is selected overwrites the instance type defined in your EC2 launch template. @@ -49 +49 @@ In the **General launch settings** section, you can define: - * **Copy private IP** : Select if you want AWS Application Migration Service to ensure that the private IP used by the test or cutover instance matches the private IP used by the source server. If selected, AWS Application Migration Service monitors the source server on an hourly basis to identify the Private IP and uses the private IP of the primary network interface. Make sure that the IP range of the subnet you set in the EC2 Launch Template includes the private IP address for this feature to work. Copy private IP is not supported for IPv6. + * **Copy private IP** : Select if you want AWS Transform MGN to ensure that the private IP used by the test or cutover instance matches the private IP used by the source server. If selected, AWS Transform MGN monitors the source server on an hourly basis to identify the Private IP and uses the private IP of the primary network interface. Make sure that the IP range of the subnet you set in the EC2 Launch Template includes the private IP address for this feature to work. Copy private IP is not supported for IPv6. @@ -51 +51 @@ In the **General launch settings** section, you can define: - * **Transfer server tags** : Select if you want AWS Application Migration Service to transfer user-configured custom tags from your source servers to your test or cutover instance. If selected, server tags are transferred. These tags are attached to all source servers, all launched test and cutover instances, and all of the ephemeral resources that are created on your AWS account during the normal operation of AWS Application Migration Service, such as snapshots, Amazon EBS volumes, replication and conversion servers, and security groups. + * **Transfer server tags** : Select if you want AWS Transform MGN to transfer user-configured custom tags from your source servers to your test or cutover instance. If selected, server tags are transferred. These tags are attached to all source servers, all launched test and cutover instances, and all of the ephemeral resources that are created on your AWS account during the normal operation of AWS Transform MGN, such as snapshots, Amazon EBS volumes, replication and conversion servers, and security groups. @@ -59 +59 @@ For Windows servers choose if you want to **BYOL**)”. This sets set up a Dedic - * **Boot mode** : When a computer boots, the first software that it runs is responsible for initializing the platform and providing an interface for the operating system to perform platform-specific operations. In Amazon EC2, two variants of the boot mode software are supported: Unified Extensible Firmware Interface (UEFI) and Legacy BIOS. The boot mode allows Application Migration Service to launch a test or cutover instance type that best matches the configuration of the source server. You can select between **Keep the source boot mode** or change it to **BIOS/UEFI modes** . + * **Boot mode** : When a computer boots, the first software that it runs is responsible for initializing the platform and providing an interface for the operating system to perform platform-specific operations. In Amazon EC2, two variants of the boot mode software are supported: Unified Extensible Firmware Interface (UEFI) and Legacy BIOS. The boot mode allows MGN to launch a test or cutover instance type that best matches the configuration of the source server. You can select between **Keep the source boot mode** or change it to **BIOS/UEFI modes** . @@ -87 +87 @@ If this setting is not chosen, the default volume type selected in the launch te -Note: if you manually delete the default launch template, AWS Application Migration Service generates a new default launch template. Any changes previously made to the default template are discarded, including subnet and security groups. You can make the same changes on the new launch template, and they are applied to servers you add to the console after you make the changes. +Note: if you manually delete the default launch template, AWS Transform MGN generates a new default launch template. Any changes previously made to the default template are discarded, including subnet and security groups. You can make the same changes on the new launch template, and they are applied to servers you add to the console after you make the changes. @@ -93 +93 @@ Use this setting to determine whether to apply Migration Acceleration Program (M -Select**Add MAP tag to Launched Instances** option, if you want Application Migration Service to automatically tag your launched instances with the tag key and value combination required for MAP program. Once selected you must specify the MAP tag value that is used in your MAP tagging. Application Migration Service automatically tagw your migrated resources with the key: “map-migrated” and the value of the tag that you provided. For more details about the tag value that should be used here, please refer to the MAP tagging guide provided in your MAP term. +Select**Add MAP tag to Launched Instances** option, if you want MGN to automatically tag your launched instances with the tag key and value combination required for MAP program. Once selected you must specify the MAP tag value that is used in your MAP tagging. MGN automatically tagw your migrated resources with the key: “map-migrated” and the value of the tag that you provided. For more details about the tag value that should be used here, please refer to the MAP tagging guide provided in your MAP term.