2 Answers
- Newest
- Most votes
- Most comments
4
There is no need to upgrade your MongoDB version, DMS supports MongoDB version 3.0+. The documentation at https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html merely states that support for MongoDB 4.2 and 4.4 was added in DMS version 3.4.5.
answered a year ago
3
you'll need to consider alternative methods
- Upgrade your MongoDB instances to a supported version before using AWS DMS
- Perform a live migration using a custom script or tool Write a custom script or use a third-party tool (e.g., Apache Nifi, Talend, or custom-built solutions) to perform a live migration of the data from your MongoDB 3.2.x instances to AWS DocumentDB.
nice info bro. cheers.
Relevant content
- asked 10 months ago
- Accepted Answerasked a year ago
- asked 3 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
ya, but it strange since I can't connect to mongodb 3.2.xx from AWS DMS. Already reachable via AWS Reachability Analysis, BindIP -> I've setup it already. So I assume it because of wire protocol from mongodb version 3.2.xx.
MongoServerSelectionError: Server at xxxxxx:27017 reports maximum wire version 4, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6). I event can't connect from other server. :)