Docs Menu
Docs Home
MongoDB Cloud Manager

MongoDB Compatibility Matrix

On this page

  • MongoDB Versions Compatible with Cloud Manager
  • Agent Compatibility
  • MongoDB Deployment Types

This page describes compatibility between Cloud Manager features and MongoDB.


Cloud Manager support for End of Life MongoDB versions

Cloud Manager doesn't support Backup, Monitoring, or Automation for versions earlier than MongoDB 3.6.

  • Cloud Manager can automate deployments running MongoDB versions 3.6 or later.

  • Cloud Manager can monitor deployments running MongoDB versions 3.6 or later.

  • Cloud Manager can back up deployments running MongoDB versions 3.6 or later.

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

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

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

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

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.

← Reference