AWS mgn documentation change
Summary
Updated verb tenses and grammatical structure for consistency (e.g., 'will use' to 'uses', 'will result' to 'results') without changing technical meaning
Security assessment
Changes are purely grammatical/editorial improvements with no security context or vulnerability references
Diff
diff --git a/mgn/latest/ug/key-considerations.md b/mgn/latest/ug/key-considerations.md index d6bd6552b..a58d4a9e5 100644 --- a//mgn/latest/ug/key-considerations.md +++ b//mgn/latest/ug/key-considerations.md @@ -13 +13 @@ 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 will use 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 will utilize the right-sizing instance. +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. @@ -19 +19 @@ If you change your instance type and do not deactivate the instance right-sizing -Customers that do not have a default VPC must modify the EC2 launch template and explicitly define the subnet in which to launch. Failure to do so will result in errors when launching test or cutover instances. +Customers that do not have a default VPC must modify the EC2 launch template and explicitly define the subnet in which to launch. Failure to do so results in errors when launching test or cutover instances. @@ -23 +23 @@ Customers that do not have a default VPC must modify the EC2 launch template and - 4. **Private IP and Subnet** – Each subnet contains a CIDR block of IP ranges. If you use the **Copy private IP** feature, then ensure that this IP is included in the CIDR block range. Otherwise, instance launch will fail. + 4. **Private IP and Subnet** – Each subnet contains a CIDR block of IP ranges. If you use the **Copy private IP** feature, then ensure that this IP is included in the CIDR block range. Otherwise, instance launch fails. @@ -27 +27 @@ Customers that do not have a default VPC must modify the EC2 launch template and - 6. **Network interfaces** – 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. + 6. **Network interfaces** – 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. @@ -35 +35 @@ 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 will be 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 Application Migration Service. @@ -43 +43 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t - 13. **Volumes** – For each EBS volume, the service uses the user-selected values. If no matching volume exists in the launch template, the service will the default value. If the launch template includes a volume that does not exist in the source server, the system will disregard the specific volume. + 13. **Volumes** – For each EBS volume, the service uses the user-selected values. If no matching volume exists in the launch template, the service uses the default value. If the launch template includes a volume that does not exist in the source server, the system disregards the specific volume. @@ -45 +45 @@ If you wish to use an Elastic IP, you must create an ENI to specify the IP and t -If you delete the EC2 launch template, the service will create a new one with default values. +If you delete the EC2 launch template, the service creates a new one with default values.