AWS Security ChangesHomeSearch

AWS mgn: MGN quick start guide restructured with IAM initialization note

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

File: mgn/latest/ug/quick-start-guide-gs.md · Type: iam

Summary

Rewrites the AWS Transform MGN quick start guide into a step-by-step migration checklist and adds a note that service initialization requires an IAM user with the AdministratorAccess managed policy attached.

Security assessment

The diff is primarily a documentation restructure of the MGN quick start guide. The only security-relevant line mentions using an IAM user with AdministratorAccess for initialization, which is permission guidance but does not address a specific vulnerability, incident, or new security feature.

Evidence

+  * To [initialize the service](./mgn-initialize-console.html), you use an IAM user with the AdministratorAccess managed policy attached.

Diff

diff --git a/mgn/latest/ug/quick-start-guide-gs.md b/mgn/latest/ug/quick-start-guide-gs.md
index aaed6ae..bc0dffa 100644
--- a//mgn/latest/ug/quick-start-guide-gs.md
+++ b//mgn/latest/ug/quick-start-guide-gs.md
@@ -6,0 +7,2 @@
+Before you beginStep 1: Initialize the serviceStep 2: Add source serversStep 3: Review launch settingsStep 4: Launch and validate test instancesStep 5: Launch cutover instancesStep 6: Complete the migration
+
@@ -9 +11,92 @@
-Follow this guide to set up AWS Transform MGN for the first time, including:
+This quick start is a high-level checklist of the AWS Transform MGN migration flow. Each step links to the detailed instructions for that step.
+
+## Before you begin
+
+Before you start the migration, make sure that:
+
+  * To [initialize the service](./mgn-initialize-console.html), you use an IAM user with the AdministratorAccess managed policy attached.
+
+  * AWS Transform MGN is [available in your target AWS Region](./what-is-mgn.html#supported-regions).
+
+  * Your source environment and AWS network meet the [network requirements](./preparing-environments.html), including the required ports.
+
+
+
+
+The following diagram shows the network architecture for AWS Transform MGN.
+
+![Data replication from corporate data center through AWS Replication Agent to staging area and migrated resources in AWS.](/images/mgn/latest/ug/images/AWSMGNArchitecture.png)
+
+The service is free for each server for 2,160 hours, which is 90 days when used continuously, but you pay for the AWS resources you provision during the migration. Learn more about [costs during migration](./adding-servers.html).
+
+## Step 1: Initialize the service
+
+AWS Transform MGN must be initialized in each AWS Region in which you plan to use it. When you initialize MGN with the console, the initialization process creates your replication template, which determines how data is replicated from your source servers to AWS.
+
+Learn more about [initializing MGN with the console](./mgn-initialize-console.html) and the [replication template](./replication-settings-template.html).
+
+## Step 2: Add source servers
+
+Add source servers to AWS Transform MGN by installing the AWS Replication Agent on them.
+
+How you know you're done: in the **Source servers** list, the **Migration lifecycle** column shows **Not ready** while the initial sync runs, and changes to **Ready for testing** when the initial sync is complete. The **Data replication status** column shows **Healthy** when all data has been copied and changes are replicated continuously.
+
+Learn more about [adding source servers](./adding-servers.html), [installing the AWS Replication Agent](./agent-installation.html), and the [migration lifecycle](./source-server-migration-metrics.html#source-server-migration-metrics-lifecycle).
+
+## Step 3: Review launch settings
+
+Launch settings determine how a test or cutover instance is launched for each source server in AWS. AWS Transform MGN creates them automatically, including the Amazon EC2 launch template, each time you add a source server, and you can modify them at any time.
+
+Learn more about [launch settings](./launch-settings.html) and [reviewing launch settings for a source server](./launch-settings-source.html).
+
+## Step 4: Launch and validate test instances
+
+Launch test instances to verify that your source servers function properly in AWS before you initiate a cutover.
+
+What you do:
+
+  * Check that the server shows **Ready for testing** and **Healthy** , then choose **Test and cutover** , then under **Testing** , choose **Launch test instances**.
+
+  * Connect to each test instance with SSH (Linux) or RDP (Windows), validate connectivity, and run acceptance tests for your application.
+
+  * When testing is complete, choose **Test and cutover** , then under **Testing** , choose **Mark as "Ready for cutover"**.
+
+
+
+
+How you know you're done: the **Migration lifecycle** column changes from **Test in progress** to **Ready for cutover**.
+
+###### Tip
+
+You can test as many times as you need. Each new test replaces the previous test instance, and data replication continues. You are billed for test instances, so terminate them when you no longer need them.
+
+Learn more about [launching test instances](./launching-test-servers.html) and [marking servers as Ready for cutover](./finalizing-test.html).
+
+## Step 5: Launch cutover instances
+
+After you finalize testing for your source servers, launch cutover instances at a set date and time. The cutover migrates your source servers to the cutover instances in AWS.
+
+What you do:
+
+  * Confirm that the server shows **Ready for cutover** , that **Data replication status** is **Healthy** , and that there is no lag.
+
+  * Stop all operational services on the source server. We recommend that you shut down the source server so that it doesn't drift from the cutover instance. Don't reboot source servers before the cutover.
+
+  * Choose **Test and cutover** , then under **Cutover** , choose **Launch cutover instances**.
+
+  * Connect to the cutover instances with SSH or RDP and validate your application.
+
+
+
+
+How you know you're done: the **Migration lifecycle** column shows **Cutover in progress**.
+
+Learn more about [launching cutover instances](./launch-cutover.html).
+
+## Step 6: Complete the migration
+
+After you confirm that the cutover instance works as expected, finalize the cutover. Then disconnect the source server from AWS Transform MGN, and archive or delete the source server.
+
+###### Important
+
+Don't disconnect a source server until the cutover instance works correctly. You might need to fall back to the source server, and restarting replication requires reinstalling the agent.
@@ -11 +104 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-###### Topics
+What you do:
@@ -13 +106 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-  * [First time setup](./first-time-setup-gs.html)
+  * Choose **Test and cutover** , then choose **Finalize cutover**. This stops data replication, discards replicated data, terminates replication resources, and sends the AWS Replication Agent a command to uninstall itself (typically up to 10 minutes).
@@ -15 +108 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-  * [Adding source servers](./adding-servers-gs.html)
+  * Choose **Actions** , then choose **Disconnect from service**.
@@ -17 +110 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-  * [Configuring launch settings](./configuring-target-gs.html)
+  * Choose **Actions** , then choose **Mark as archived**.
@@ -19 +111,0 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-  * [Launching a test instance](./launching-test-gs.html)
@@ -21 +112,0 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
-  * [Launching a cutover instance](./launch-cutover-gs.html)
@@ -23,0 +115 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
+How you know you're done: after you finalize the cutover, the **Migration lifecycle** column shows **Cutover complete** , and the **Next step** column shows **Mark as archived**.
@@ -24,0 +117 @@ Follow this guide to set up AWS Transform MGN for the first time, including:
+Learn more about [managing source servers after migration](./server-post-migration.html), including how to [finalize the cutover](./server-post-migration.html#server-post-migration-finalize-cutover), [disconnect the source server](./server-post-migration.html#server-post-migration-disconnect), and [archive the source server](./server-post-migration.html#server-post-migration-archive).
@@ -34 +127 @@ What Is AWS Transform MGN?
-First time setup
+Getting started