AWS mgn documentation change
Summary
Updated service branding from 'Application Migration Service' to 'AWS Transform MGN' throughout the documentation. Changed references to 'Application Migration Service' to 'AWS Transform MGN' or 'MGN' in multiple sections including introductions, AMI configuration, instance types, volume settings, network configurations, and warnings.
Security assessment
The changes are purely branding updates with no evidence of security vulnerability fixes, security patches, or new security documentation. All modifications involve service name replacements without altering security configurations, warnings, or protocols.
Diff
diff --git a/mgn/latest/ug/detailed-considerations.md b/mgn/latest/ug/detailed-considerations.md index b27242b9d..368b41a35 100644 --- a//mgn/latest/ug/detailed-considerations.md +++ b//mgn/latest/ug/detailed-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) @@ -11 +11 @@ NEW - You can now accelerate your migration and modernization with AWS Transform -This section reviews the entire EC2 launch template and identifies which fields should and should not be changed in order for the EC2 launch template to work with Application Migration Service. Editing or changing any fields that are marked as "do not edit" or "do not change" can cause AWS Application Migration Service to not function. +This section reviews the entire EC2 launch template and identifies which fields should and should not be changed in order for the EC2 launch template to work with Application Migration Service. Editing or changing any fields that are marked as "do not edit" or "do not change" can cause AWS Transform MGN to not function. @@ -20 +20 @@ This section reviews the entire EC2 launch template and identifies which fields - * **AMI** – Customers do not typically choose a specific AMI to include in the launch template. If you edit the launch template to use an existing AMI, the contents of the AMI are not used by AWS Application Migration Service. If the AMI is not configured properly (licensing, flags, and more), then this may prevent the test or cutover instance launched from booting correctly or from being properly licensed. + * **AMI** – Customers do not typically choose a specific AMI to include in the launch template. If you edit the launch template to use an existing AMI, the contents of the AMI are not used by AWS Transform MGN. If the AMI is not configured properly (licensing, flags, and more), then this may prevent the test or cutover instance launched from booting correctly or from being properly licensed. @@ -25 +25 @@ This section reviews the entire EC2 launch template and identifies which fields - * **Instance type** – You can select any instance type you want. The launch template shows the instance type suggested by AWS Application Migration Service. + * **Instance type** – You can select any instance type you want. The launch template shows the instance type suggested by AWS Transform MGN. @@ -58 +58 @@ Each disk is composed of the following fields: - * **Volume type** – You can select any volume type you want to use. AWS Application Migration Service automatically sets **General Purpose SSD (gp3)** as the default. You may want to change the volume type in order to reduce costs. Ensure that you read the caveats in the [EBS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html#initialize). + * **Volume type** – You can select any volume type you want to use. AWS Transform MGN automatically sets **General Purpose SSD (gp3)** as the default. You may want to change the volume type in order to reduce costs. Ensure that you read the caveats in the [EBS documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html#initialize). @@ -68 +68 @@ Each disk is composed of the following fields: -AWS Application Migration Service automatically provisions the maximum IOPS possible for the volume, based on the above ratio. This is to minimize the impact of the [performance penalty](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html#initialize) when working with EBS volumes created from snapshots. +AWS Transform MGN automatically provisions the maximum IOPS possible for the volume, based on the above ratio. This is to minimize the impact of the [performance penalty](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html#initialize) when working with EBS volumes created from snapshots. @@ -74 +74 @@ AWS Application Migration Service automatically provisions the maximum IOPS poss - * **Remove (volume)** – **Do not** use this functionality. You cannot remove volumes from the source server through the launch template. If you do, Application Migration Service automatically creates a volume using the default volume settings. + * **Remove (volume)** – **Do not** use this functionality. You cannot remove volumes from the source server through the launch template. If you do, MGN automatically creates a volume using the default volume settings. @@ -93 +93 @@ The following storage parameters: **Volume initialization rate** , **EBS card in - * **Resource tags** – You can add up to 50 tags. These are transferred to your test and cutover instances. Note that these tags may interfere with other tags that have already been added to the source server. Launch template tags always take precedence over tags set in the Application Migration Service console or tags manually assigned to the server. + * **Resource tags** – You can add up to 50 tags. These are transferred to your test and cutover instances. Note that these tags may interfere with other tags that have already been added to the source server. Launch template tags always take precedence over tags set in the MGN console or tags manually assigned to the server. @@ -110 +110 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Subnet** – Choose the subnet. This is the subnet within which the network interface is located and the test or cutover instance is launched. AWS Application Migration Service selects the default VPC subnet by default (if one exists). + * **Subnet** – Choose the subnet. This is the subnet within which the network interface is located and the test or cutover instance is launched. AWS Transform MGN selects the default VPC subnet by default (if one exists). @@ -114 +114 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Primary IP** – Use this field if you wish to utilize a private IP. The private IP you set in the **Copy private IP** field in the Application Migration Service launch settings is copied to this field. + * **Primary IP** – Use this field if you wish to utilize a private IP. The private IP you set in the **Copy private IP** field in the MGN launch settings is copied to this field. @@ -133 +133 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Advanced details** – In this section, we focus on the fields you should **not** change or edit in order to allow AWS Application Migration Service to function properly. **Do not** change or edit any of the following fields: + * **Advanced details** – In this section, we focus on the fields you should **not** change or edit in order to allow AWS Transform MGN to function properly. **Do not** change or edit any of the following fields: