Skip to content

Commit 1363bcc

Browse files
rob-mongodbjdestefano-mongo
authored andcommitted
(DOCSP-4003) Clarify that auth is optional for Live Migration. (#127)
* (DOCSP-4003) Clarify that auth is optional for Live Migration. * (DOCSP-4003) Review by Steve. * (DOCSP-4003) Review comment by Steve. * (DOCSP-4003) Resolve merge conflicts.
1 parent 195dace commit 1363bcc

File tree

3 files changed

+62
-70
lines changed

3 files changed

+62
-70
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99

1010
time: 20
1111
prerequisites:
12-
.. include:: /includes/steps/migration_pr.rst
12+
.. include:: /includes/migration_pr.rst
1313
check_your_environment:
1414
procedure:
1515
.. include:: /includes/steps/migrate-to-atlas.rst

source/includes/migration_pr.rst

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
* **Your data is currently in a MongoDB database.**
2+
3+
This guide focuses on migrating to Atlas from an existing MongoDB deployment
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>`_
6+
for help with your migration.
7+
8+
* **Your current MongoDB database is running MongoDB 2.6 or higher.**
9+
10+
Atlas supports the latest versions of MongoDB: 3.4, 3.6, and 4.0.
11+
If you're running MongoDB version 2.6 or greater, the Atlas Live Migration
12+
Service can move your data directly into a newer database version.
13+
Update your `MongoDB drivers <https://docs.mongodb.com/ecosystem/drivers>`_
14+
and make any necessary code changes at the application level to ensure
15+
compatibility. If you're running a version older than 2.6, see
16+
`Upgrade MongoDB to 2.6 <https://docs.mongodb.com/v2.6/release-notes/2.6-upgrade/index.html>`_
17+
for upgrade instructions.
18+
19+
* **Your current deployment is a MongoDB replica set or sharded cluster.**
20+
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>`.
23+
Live migration of data from sharded clusters is not supported.
24+
25+
* **(Optional) Enabled authentication on your source deployment.**
26+
27+
The migration process requires that authentication is enabled on your
28+
source cluster in AWS. See :manual:`Enable Auth </tutorial/enable-authentication>`
29+
for instructions on enabling authentication.
30+
You can verify that authentication is enabled on your source cluster
31+
using the :manual:`mongo </reference/program/mongo/>` command:
32+
33+
.. code-block:: sh
34+
35+
mongo <mongodb-connection-string> -u <mongodb-username> -p --authenticationDatabase admin
36+
37+
* **The database user from your source cluster on AWS that you will use to perform the migration has the required MongoDB roles.**
38+
39+
The user must have the :authrole:`clusterMonitor` and :authrole:`backup` roles. To verify
40+
that the database user that you intend to use for migration has the appropriate
41+
roles, run the :manual:`db.getUser() </reference/method/db.getUser>` command against the admin database.
42+
43+
.. code-block:: javascript
44+
45+
use admin
46+
db.getUser("admin")
47+
{
48+
"_id" : "admin.admin",
49+
"user" : "admin",
50+
"db" : "admin",
51+
"roles" : [
52+
{
53+
"role" : "backup",
54+
"db" : "admin"
55+
},
56+
{
57+
"role" : "clusterMonitor",
58+
"db" : "admin"
59+
}
60+
]
61+
} ...

source/includes/steps-migration_pr.yaml

Lines changed: 0 additions & 69 deletions
This file was deleted.

0 commit comments

Comments
 (0)