This section describes the requirements for the hosts that run the MongoDB Agent.
Hosts that run MongoDB Agents must run on a 64-bit version of one of the following hardware architectures and operating systems. The following table lists the MongoDB Server versions that you can deploy with the MongoDB Agent on the associated platforms:
RHEL/CentOS/Oracle Linux 7
RHEL/Rocky/Alma Linux/Oracle Linux 8 1
RHEL/Rocky/Alma Linux/Oracle Linux 9 1
Amazon Linux 2
Amazon Linux 2023
Debian 8 2
Debian 9 2
Debian 10 2
Debian 11 2
Ubuntu 22.x 3
Amazon Linux 2
Amazon Linux 2023
RHEL/ Centos 7
RHEL/ Centos 8
1 The Rocky or Alma Linux OS
must include the
2 The Debian installation must include the
lsb-release package. To learn more, see lsb-release.
3 MongoDB Connector for BI isn't supported on Ubuntu 22.04.
The MongoDB Agent must run on 64-bit architectures.
MongoDB recommends a minimum of 2 CPU cores and 2 GB of RAM for MongoDB Agent hosts.
If you activate backup, all MongoDB Agent hosts require at least an additional 2 CPU cores and 3 GB of RAM beyond basic platform requirements. Each backup job that the MongoDB Agent runs further impacts host performance.
The hosts that serve the MongoDB deployments must:
Have full network access to each other through their Fully Qualified Domain Names (FQDNs). Each host must reach each other host through the FQDN.
Permit Automation to start mongod on a random ephemeral port and connect to that port when restoring your deployment from a backup.
Resolve each FQDN to a unique IP address. Run the following command in the shell to resolve the FQDN:
dig +short myip.opendns.com @resolver1.opendns.com
Set the Common Name or Subject Alternative Name value of any SSL certificates to the MongoDB host's FQDN.
The network configuration must allow each MongoDB Agent to make a direct connection to each MongoDB deployment listed on the Deployment page. Ops Manager does not support port forwarding.
If you install the MongoDB Agent on a host that is running a MongoDB process, the agent must have:
Permission to stop any MongoDB processes. The MongoDB Agent restarts the process using the Agent's own set of MongoDB binaries. If you installed MongoDB with a package manager, use the same package manager to install the MongoDB Agent. This gives the MongoDB Agent the same owner as MongoDB.
Writepermissions on the MongoDB data directory and log directory.
If you deploy the MongoDB Agent to a host that doesn't have MongoDB
installed, ensure the user that owns the MongoDB Agent has
Write permissions on the MongoDB data and log directories you plan
The MongoDB Agent requires one Agent API Key per project to communicate with the Ops Manager Application.
If you do not have an existing Agent API Key for your Ops Manager project, create one:
Navigate to Agents.
Click Agent API Keys.
This button appears if:
The current user is the
The project has no Agent API Keys other than the Original Group API Key with an exclamation next to it. This type of key exists in projects created before the new Agent API Key model. In the new model, you can create multiple Agent API Keys in a project, and any the project's MongoDB Agents can use any of the keys.
In the Generate Key modal, provide a description of the new Agent API Key in the Description box.
When you generate an Agent API Key, Ops Manager displays it one time only. You must copy this key. Treat it like a password; store it in a secure place. Ops Manager never displays the full key again.