AWS prescriptive-guidance documentation change
Summary
Updated console references from 'Application Migration Service console' to 'MGN console'
Security assessment
Service name abbreviation update without any modifications to security procedures, access controls, or vulnerability disclosures.
Diff
diff --git a/prescriptive-guidance/latest/migration-factory-cloudendure/step3.md b/prescriptive-guidance/latest/migration-factory-cloudendure/step3.md index 86419be22..1249bcb24 100644 --- a//prescriptive-guidance/latest/migration-factory-cloudendure/step3.md +++ b//prescriptive-guidance/latest/migration-factory-cloudendure/step3.md @@ -11 +11 @@ After installing the replication agent on the source machines, you monitor the s -If you have a small migration, you can verify the replication status manually from the Application Migration Service console. However, if you have large-scale migrations, servers across multiple projects, and servers in multiple waves, this verification can be difficult. For example, if you have 100 servers in wave 1, you must repeat the following steps 100 times to verify their replication status: +If you have a small migration, you can verify the replication status manually from the MGN console. However, if you have large-scale migrations, servers across multiple projects, and servers in multiple waves, this verification can be difficult. For example, if you have 100 servers in wave 1, you must repeat the following steps 100 times to verify their replication status: @@ -15 +15 @@ If you have a small migration, you can verify the replication status manually fr - * Log in to the Application Migration Service console, and then search for the server name. + * Log in to the MGN console, and then search for the server name.