|
2 | 2 |
|
3 | 3 | This guide focuses on migrating to Atlas from an existing MongoDB deployment |
4 | 4 | on AWS. If you have data in other database systems, such as MySQL, PostgreSQL, or |
5 | | - DynamoDB, please `contact us <https://mongodbcom-node-staging-2.corp.mongodb.com/contact>`_ |
| 5 | + DynamoDB, please `contact us <https://mongodb.com/contact>`_ |
6 | 6 | for help with your migration. |
7 | 7 |
|
8 | 8 | * Your current MongoDB database is running MongoDB 2.6 or higher. |
9 | 9 |
|
10 | 10 | Atlas supports the latest versions of MongoDB: 3.6, 4.0, and 4.2. |
11 | 11 | If you're running MongoDB version 2.6 or greater, the Atlas Live Migration |
12 | 12 | Service can move your data directly into a newer database version. |
13 | | - Update your `MongoDB drivers <https://docs.mongodb.com/ecosystem/drivers>`_ |
| 13 | + Update your `MongoDB drivers <https://docs.mongodb.com/drivers/>`_ |
14 | 14 | and make any necessary code changes at the application level to ensure |
15 | 15 | compatibility. If you're running a version older than 2.6, see |
16 | 16 | `Upgrade MongoDB to 2.6 <https://docs.mongodb.com/v2.6/release-notes/2.6-upgrade/index.html>`_ |
|
19 | 19 | * Your current deployment is a MongoDB replica set or sharded cluster. |
20 | 20 |
|
21 | 21 | If your deployment is currently a standalone instance, you must first |
22 | | - :manual:`convert it to a replica set </tutorial/convert-standalone-to-replica-set>`. |
| 22 | + :manual:`convert it to a replica set </tutorial/convert-standalone-to-replica-set/>`. |
23 | 23 |
|
24 | 24 | * (Optional) Enabled authentication on your source deployment. |
25 | 25 |
|
26 | 26 | The migration process requires that authentication is enabled on your |
27 | | - source cluster in AWS. See :manual:`Enable Auth </tutorial/enable-authentication>` |
| 27 | + source cluster in AWS. See :manual:`Enable Auth </tutorial/enable-authentication/>` |
28 | 28 | for instructions on enabling authentication. |
29 | 29 | You can verify that authentication is enabled on your source cluster |
30 | 30 | using the :manual:`mongo </reference/program/mongo/>` command: |
|
37 | 37 |
|
38 | 38 | The user must have the :authrole:`clusterMonitor` and :authrole:`backup` roles. To verify |
39 | 39 | that the database user that you intend to use for migration has the appropriate |
40 | | - roles, run the :manual:`db.getUser() </reference/method/db.getUser>` command against the admin database. |
| 40 | + roles, run the :manual:`db.getUser() </reference/method/db.getUser/>` command against the admin database. |
41 | 41 |
|
42 | 42 | .. code-block:: javascript |
43 | 43 |
|
|
0 commit comments