AWS Security ChangesHomeSearch

AWS mgn: MGN post-migration doc: wording updates, removes termination protection note

Service: mgn · 2026-10-29 · Documentation low

File: mgn/latest/ug/server-post-migration.md

Summary

Editorial rewording of the AWS Transform MGN post-migration guide (finalize cutover, disconnect, archive, delete steps). Notably removes the Note recommending enabling EC2 termination protection on cutover instances, and adds a statement that finalizing cutover uninstalls the AWS Replication Agent from the source server.

Security assessment

The diff is predominantly stylistic rewording (dialog -> dialog box, navigate -> go to). The only security-relevant element is the removal of the recommendation to enable EC2 termination protection on cutover instances, which is a hardening/availability best practice rather than a fix for a specific vulnerability. No CVE or incident is referenced, so it is not tied to a concrete security issue.

Evidence

-We recommend that you turn on termination protection for your cutover instances after you complete your testing and before you finalize the cutover. Learn more about enabling termination protection in [this Amazon EC2 article](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/terminating-instances.html#Using_ChangingDisableAPITermination).

Diff

diff --git a/mgn/latest/ug/server-post-migration.md b/mgn/latest/ug/server-post-migration.md
index 2030b81..c44fa5a 100644
--- a//mgn/latest/ug/server-post-migration.md
+++ b//mgn/latest/ug/server-post-migration.md
@@ -24 +24 @@ After you launch cutover instances, use the following actions to complete the mi
-Finalize the cutover after you have launched a cutover instance and confirmed that it works as expected in AWS. Finalizing the cutover changes the server's **Migration lifecycle** status to **Cutover complete** , stops data replication, and discards all replicated data. All AWS resources used for data replication are terminated.
+Finalize the cutover after you launch a cutover instance and confirm that it works as expected in AWS. Finalizing the cutover changes the server's **Migration lifecycle** status to **Cutover complete** , stops data replication, and discards all replicated data. AWS Transform MGN terminates all AWS resources used for data replication.
@@ -26,3 +26 @@ Finalize the cutover after you have launched a cutover instance and confirmed th
-###### Note
-
-We recommend that you turn on termination protection for your cutover instances after you complete your testing and before you finalize the cutover. Learn more about enabling termination protection in [this Amazon EC2 article](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/terminating-instances.html#Using_ChangingDisableAPITermination).
+Finalizing the cutover also sends a command to the AWS Replication Agent to uninstall itself from the source server. Uninstalling typically takes up to 10 minutes.
@@ -32 +30 @@ To finalize a cutover:
-  1. Validate that the cutover instance is functioning correctly in AWS, for example by testing connectivity and application behavior.
+  1. Validate that the cutover instance functions correctly in AWS, for example, by testing connectivity and application behavior.
@@ -34 +32 @@ To finalize a cutover:
-  2. Open the AWS Transform MGN console and navigate to the **Source servers** page.
+  2. Open the AWS Transform MGN console and go to the **Source servers** page.
@@ -40 +38 @@ To finalize a cutover:
-  5. In the **Finalize cutover for X servers** dialog, choose **Finalize**.
+  5. In the **Finalize cutover for X servers** dialog box, choose **Finalize**.
@@ -49,3 +47 @@ After the cutover is finalized, the **Migration lifecycle** column shows **Cutov
-After you finalize the cutover, the AWS Replication Agent receives a command to uninstall itself from the source server (within 10 minutes).
-
-If you encounter issues after finalizing, choose **Test and cutover** , then **Revert to "ready for cutover"** to return the server to the **Ready for cutover** state.
+If you encounter issues after finalizing, choose **Test and cutover** , then choose **Revert to "ready for cutover"** to return the server to the **Ready for cutover** state.
@@ -59 +55 @@ After data replication is complete, you can disconnect the source server from AW
-Do not disconnect the source server until you have confirmed that the cutover instance is working correctly in AWS. If you discover issues after cutover, you may need to fall back to the source server.
+Do not disconnect the source server until you confirm that the cutover instance works correctly in AWS. If you discover issues after cutover, you might need to fall back to the source server.
@@ -63 +59 @@ To disconnect a source server:
-  1. Open the AWS Transform MGN console and navigate to the **Source servers** page.
+  1. Open the AWS Transform MGN console and go to the **Source servers** page.
@@ -69 +65 @@ To disconnect a source server:
-  4. In the **Disconnect X server/s from service** dialog, choose **Disconnect**.
+  4. In the **Disconnect X server/s from service** dialog box, choose **Disconnect**.
@@ -82 +78 @@ To restart data replication for a disconnected server, you must reinstall the AW
-After a server is cut over, you can archive it. Archived servers are removed from the main **Source servers** list, which keeps the console organized after large migrations. Only archive servers for which you have already performed a cutover.
+After a server is cut over, you can archive it. Archiving removes servers from the main **Source servers** list, which keeps the console organized after large migrations. Only archive servers for which you have already performed a cutover.
@@ -86 +82 @@ To archive a source server:
-  1. Open the AWS Transform MGN console and navigate to the **Source servers** page.
+  1. Open the AWS Transform MGN console and go to the **Source servers** page.
@@ -92 +88 @@ To archive a source server:
-  4. In the **Archive X servers** dialog, choose **Archive**.
+  4. In the **Archive X servers** dialog box, choose **Archive**.
@@ -97 +93 @@ To archive a source server:
-To view archived servers, open the **Preferences** menu by choosing the gear button, select **Show only archived servers** , and choose **Confirm**. Clear this option to see your non-archived servers again.
+To view archived servers, choose **Archived source servers** from the drop-down menu above the source servers table. To see your active servers again, choose **Active source servers**.
@@ -101 +97 @@ To view archived servers, open the **Preferences** menu by choosing the gear but
-You can delete a source server to remove its record from AWS Transform MGN. You can delete one or more servers at a time. Only servers that are not actively replicating can be deleted.
+You can delete a source server to remove its record from AWS Transform MGN. You can delete one or more servers at a time. You can delete only servers that are not actively replicating.
@@ -105 +101 @@ To delete a source server:
-  1. Open the AWS Transform MGN console and navigate to the **Source servers** page.
+  1. Open the AWS Transform MGN console and go to the **Source servers** page.
@@ -111 +107 @@ To delete a source server:
-  4. Confirm the deletion in the dialog.
+  4. Confirm the deletion in the dialog box.