AWS migrationhub documentation change
Summary
Updated test instance guidance to require one per source server and revised cutover instructions.
Security assessment
Procedural changes for migration testing without security implications.
Diff
diff --git a/migrationhub/latest/ug/mha-managed-units.md b/migrationhub/latest/ug/mha-managed-units.md index 8ae912e45..2eb459bd3 100644 --- a/migrationhub/latest/ug/mha-managed-units.md +++ b/migrationhub/latest/ug/mha-managed-units.md @@ -123 +123 @@ ApplicationARNs | List of Application Migration Service application ARNs. | arra -After you add all of your source servers and configure their launch settings, you are ready to launch a test instance. To verify that your applications can function properly within the AWS environment, it is crucial that you test the migration of your source servers to AWS before you initiate a cutover. +After you add all of your source servers and configure their launch settings, you are ready to launch one test instance per source server. To verify that your applications can function properly within the AWS environment, it is crucial that you test the migration of your source servers to AWS before you initiate a cutover. @@ -162,3 +162 @@ ApplicationARNs | List of Application Migration Service application ARNs. | arra -After you add all of your source servers and configure their launch settings, you are ready to launch a test instance. To verify that your applications can function properly within the AWS environment, it is crucial that you test the migration of your source servers to AWS before you initiate a cutover. - -It is a best practice to perform a test at least two weeks before you plan to migrate your source servers. This time frame allows you to identify potential problems and solve them before the actual migration takes place. +After you finalize the testing of all of your source servers, you are ready for cutover. The cutover will migrate your source servers to the cutover instances on AWS.