AWS mgn documentation change
Summary
Updated verb tenses and minor grammatical improvements throughout the document for clarity (e.g., 'will show' to 'shows', 'will be transferred' to 'are transferred'). No technical content changes.
Security assessment
Changes are purely grammatical/stylistic improvements with no indication of addressing security vulnerabilities or introducing security features. Warnings about ENI settings and volume removal remain unchanged in substance.
Diff
diff --git a/mgn/latest/ug/detailed-considerations.md b/mgn/latest/ug/detailed-considerations.md index 30d917e03..e263a2763 100644 --- a//mgn/latest/ug/detailed-considerations.md +++ b//mgn/latest/ug/detailed-considerations.md @@ -16 +16 @@ 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 will not be 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 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. @@ -21 +21 @@ 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 will show 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 Application Migration Service. @@ -38 +38 @@ This section reviews the entire EC2 launch template and identifies which fields - * **Storage (volumes)** – This section will show all of the disks that you chose to replicate from your source server upon AWS Replication Agent installation. + * **Storage (volumes)** – This section shows all of the disks that you chose to replicate from your source server upon AWS Replication Agent installation. @@ -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, AWS MGN will automatically create 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, AWS MGN automatically creates a volume using the default volume settings. @@ -79 +79 @@ AWS Application Migration Service automatically provisions the maximum IOPS poss - * **Resource tags** – You can add up to 50 tags. These will be 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 AWS MGN 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 AWS MGN console or tags manually assigned to the server. @@ -88 +88 @@ AWS Application Migration Service automatically provisions the maximum IOPS poss - * **Network interface** – Use this option only if you want use a pre-existing ENI (Elastic Network Interface). The Launch Template will overwrite certain ENI settings. Use this if you want to add an Elastic IP. You will have to attach the Elastic IP to the ENI. + * **Network interface** – Use this option only if you want use a pre-existing ENI (Elastic Network Interface). The Launch Template overwrites certain ENI settings. Use this if you want to add an Elastic IP. You have to attach the Elastic IP to the ENI. @@ -96 +96 @@ 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 will be 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 Application Migration Service selects the default VPC subnet by default (if one exists). @@ -100 +100 @@ 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 AWS MGN launch settings will be 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 AWS MGN launch settings is copied to this field. @@ -106 +106 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Security groups** – Choose a security group. If no security group is chosen, then the default VPC security group will be used by default. + * **Security groups** – Choose a security group. If no security group is chosen, then the default VPC security group is used by default. @@ -108 +108 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Delete on termination** – We suggest choosing "**Yes** ". Choosing "**No** " will make this network interface a permanent ENI. + * **Delete on termination** – We suggest choosing "**Yes** ". Choosing "**No** " makes this network interface a permanent ENI. @@ -114 +114 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Add network interface** – Note that the EC2 launch template only supports two network interfaces. If you require more than two network interfaces, you will need to define them after the test or cutover instance has been launched. This can be done through a post-launch action. + * **Add network interface** – Note that the EC2 launch template only supports two network interfaces. If you require more than two network interfaces, you need to define them after the test or cutover instance has been launched. This can be done through a post-launch action. @@ -119 +119 @@ When selecting an pre-existing ENI, you must change the **Auto-assign public IP* - * **Advanced details** – In this section, we will 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 Application Migration Service to function properly. **Do not** change or edit any of the following fields: