Merge pull request #208 from terakilobyte/DOCSP-25359

Docsp 25359

Author: terakilobyte

config/redirects

@@ -11,6 +11,7 @@ raw: docs/guides/cloud/fts-stitch-sample-app -> https://developer.mongodb.com/ho
 raw: docs/tutorials/cloud/atlas-search-stitch-sample-app -> https://developer.mongodb.com/how-to/build-movie-search-application/
 raw: docs/guides/cloud/atlas-search-stitch-sample-app -> https://developer.mongodb.com/how-to/build-movie-search-application/
 raw: docs/tutorials/deploy-mongodb-with-cloud-manager -> https://www.mongodb.com/docs/cloud-manager/tutorial/nav/manage-hosts/
+raw: docs/guides/cloud/migrate-from-aws-to-atlas -> ${base}/guides/cloud/migrate-from-aws-to-atlas-on-aws
 
 # Old Guides Pages
 raw: docs/guides/realm/react-web-quickstart/ -> ${base}/realm/tutorial/ios-swift/

source/cloud/migrate-from-aws-to-atlas.txt renamed to source/cloud/migrate-from-aws-to-atlas-on-aws.txt

@@ -113,11 +113,11 @@ Procedure
 
    .. step:: Launch your target replica set in MongoDB Atlas running on AWS.
 
-      See :doc:`Create a MongoDB Account </atlas/account>` and 
-      `Create a New Cluster 
+      See :doc:`Create a MongoDB Account </atlas/account>` and
+      `Create a New Cluster
       <https://docs.atlas.mongodb.com/tutorial/create-new-cluster/>`__
       for instructions.
-   
+
       .. note::
          Your target cluster must use ``M10`` or larger instance nodes.
          For development or staging environments, deploy a cluster
@@ -135,10 +135,10 @@ Procedure
             .. figure:: /images/atlas-deployment.png
                :figwidth: 700px
                :alt: This image highlights the Migrate Data to this Cluster
-                     option on a cluster card in Atlas. 
+                     option on a cluster card in Atlas.
 
          .. step:: Click :guilabel:`General Live Migration`.
-   
+
    .. step:: Click :guilabel:`I'm ready to migrate`.
 
    .. step:: Add the IP address for the Atlas Live Migration Service on your AWS source cluster.
@@ -151,9 +151,9 @@ Procedure
 
       AWS EC2 servers are protected from unauthorized network access using
       `Security Groups <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html>`_.
-      To add new IP address ranges to the IP access list, either create a 
-      new Security Group, or modify your existing Security Group to permit 
-      inbound network access from the displayed IP address ranges. 
+      To add new IP address ranges to the IP access list, either create a
+      new Security Group, or modify your existing Security Group to permit
+      inbound network access from the displayed IP address ranges.
 
       Here is an example security group that grants access to Atlas Live Migration Service.
 
@@ -184,7 +184,7 @@ Procedure
             that Atlas will use to perform the data migration.
 
             .. note::
-            
+
                The address must be resolvable over the public internet, so do not use
                the private IP address of the node.
 
@@ -228,21 +228,21 @@ Procedure
 
             1. Stop your application. This ensures that no additional writes
                are generated to the source cluster.
-       
+
             #. Wait for the optime gap to reach zero. When the counter reaches
                zero, the source and destination clusters are in sync.
-       
+
             #. Restart your application using the new connection string
                provided in step 3 of the Live Migrate cutover UI.
-       
+
                .. step:: Once you are prepared to cut your applications over to the
                   destination Atlas cluster, click :guilabel:`Prepare to Cutover`.
 
          .. step:: Once you have completed the cutover procedure and confirmed
             your applications are working normally with the Atlas cluster,
             click :guilabel:`Cut Over` to complete the migration procedure.
             This allows Atlas to:
-       
+
             - Mark the migration plan as complete.
             - Remove the Application Server subnets from the destination
               cluster IP access list.
@@ -263,6 +263,6 @@ Summary
 You created an Atlas cluster, migrated data from your previous AWS
 MongoDB cluster, and updated your applications to use the new
 MongoDB Atlas cluster running on AWS. For more information on the
-data migration process, see `Live Migrate Your Replica Set to Atlas 
+data migration process, see `Live Migrate Your Replica Set to Atlas
 <https://docs.atlas.mongodb.com/import/live-import/>`_ and
 `mongomirror <https://docs.atlas.mongodb.com/reference/mongomirror/index.html>`_.