Stuck with connectivity failures between AWS DMS and a MongoDB? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support Techs resolve this AWS error.

How to resolve connectivity failures between AWS DMS and a MongoDB?

A MongoDB source endpoint can fail to connect for several reasons.

Today, let us see the common reasons and steps followed by our Support Techs to resolve them.

1.Connection timeout calling errors

Typically, error looks as shown below:

Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed to create new client connection Failed to connect to database., Application-Detailed-Message: Error verifying connection: 'No suitable servers found (`serverSelectionTryOnce` set): [connection timeout calling ismaster on 'mongodbtest.us-west-2.compute.amazonaws.com:27017']' Failed to connect to database.

Usually, this error occurs when connectivity can’t establish between the AWS DMS replication instance to the MongoDB database.

Most often, this is caused by configuration issues in the security groups, network access control lists (network ACLs), or on-premises firewalls and IP address tables.

To resolve this error, confirm that your network is configure to meet the connectivity requirements for AWS DMS replication instances.

2.Connection refused calling errors

When the connection request from the AWS DMS replication instance is refuse by the MongoDB instance, you receive the following error:

Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed to create new client connection Failed to connect to database., Application-Detailed-Message: Error verifying connection: 'No suitable servers found (`serverSelectionTryOnce` set): [connection refused calling ismaster on 'mongodbtest.us-west-2.compute.amazonaws.com:27017']' Failed to connect to database.

This error occurs when the the bindIp settings on the MongoDB database don’t allow access to connections from replication instances.

To resolve this error, modify the bindIp configuration on the MongoDB instance to allow connections from replication instances.

3.Authentication failed errors

Usually, when the credentials provided aren’t correct or use a special character, you receive the following error:

Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed to create new client connection Failed to connect to database., Application-Detailed-Message: Error verifying connection: 'Authentication failed.' Failed to connect to database.

This error occurs when the user name or password provided in the endpoint are incorrect.

Secondly, the authentication source database provided the for the user name field is incorrect.

Else you used a special character in your password that MongoDB doesn’t accept.

To resolve this error, confirm that you have the correct authentication credentials by connecting to the MongoDB database using the user name and password provided in the endpoint.

4.Libmongoc version errors

Usually, error occurs when you use a version of MongoDB that isn’t support for AWS DMS replication.

Typical error looks as shown below:

Test Endpoint failed: Application-Status: 1020912, Application-Message: Failed to create new client connection Failed to connect to database., Application-Detailed-Message: Error verifying connection: 'Server at ec2-35-166-73-109.us-west-2.compute.amazonaws.com:27017 reports wire version 2, but this version of libmongoc requires at least 3 (MongoDB 3.0)' Failed to connect to database.

To resolve this error, upgrade the source MongoDB database to a version of MongoDB that is supported by AWS DMS.

[Need help with more AWS error? We’d be happy to assist you]

Conclusion

To conclude, here we saw how our Support Techs resolve connectivity failures between AWS DMS and a MongoDB.