You were redirected from a different version of the documentation. Click here to go back.

MongoDB Compatibility Matrix

This page describes compatibility between Cloud Manager features and MongoDB.

Cloud Manager supports certain End of Life versions

MongoDB 3.6 reached its End of Life date on April 30, 2021. Cloud Manager doesn’t support Automation for MongoDB 2.6, 3.0, or 3.2. Cloud Manager still supports Automation using the MongoDB Agent for clusters running MongoDB 3.4 and 3.6.

MongoDB Versions Compatible with Cloud Manager

  • Cloud Manager can automate MongoDB deployments running at least the 4.0 release series.
  • Cloud Manager can monitor MongoDB deployments running at least the 2.6 release series.
  • Cloud Manager can back up MongoDB deployments running at least the 2.6 release series.

Backup Considerations for MongoDB 4.2 and 4.4

Backup support for the following MongoDB versions is growing but currently limited:

  • 4.2 with "featureCompatibilityVersion" : 4.2
  • 4.4 with "featureCompatibilityVersion" : 4.4

Support will be extended in future releases of Cloud Manager.

To learn more about backup considerations specific to MongoDB 4.2 and 4.4, see Backup Considerations.

See also

To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.

Agent Compatibility

Monitoring Compatibility

To monitor a deployment running MongoDB 3.6 or later release series, you must use Monitoring Agent version 2.7.0 or later.

Automation PowerPC Compatibility

To manage PowerPC Linux-based hosts, you must use Automation Agent or later.

MongoDB Deployment Types

Using Cloud Manager, you can configure all MongoDB deployment types: sharded clusters, replica sets, and standalones.

The shards in a sharded cluster must be replica sets. That is, a shard cannot be a standalone mongod. If you must run a shard as a single mongod (which provides no redundancy or failover), run the shard as a single-member replica set.


You may not upgrade a sharded MongoDB deployment to version 3.4 if the deployment uses mirrored mongod instances as config servers. To allow the sharded deployment to be upgraded, see Convert Config Servers to a Replica Set. The conversion requires that the sharded deployment run MongoDB version 3.2.4 or later. Deployments running previous versions must upgrade to version 3.2.4 before an upgrade to version 3.4.