On this page
MongoDB Atlas is a hosted MongoDB service option in the cloud which requires no installation overhead and offers a free tier to get started.
Use this tutorial to install MongoDB 7.0 Community Edition on
Red Hat Enterprise Linux, CentOS Linux, or Oracle Linux
 using the
yum package manager.
This tutorial installs MongoDB 7.0 Community Edition. To install a different version of MongoDB Community, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
RHEL / CentOS Stream / Oracle / Rocky / AlmaLinux 9
RHEL / CentOS Stream / Oracle / Rocky / AlmaLinux 8
RHEL / CentOS / Oracle 7
MongoDB only supports the 64-bit versions of these platforms.
MongoDB 7.0 Community Edition on RHEL / CentOS / Oracle / Rocky / AlmaLinux also supports the ARM64 architecture on select platforms.
See Platform Support for more information.
|||(1, 2) MongoDB only supports Oracle Linux running the Red Hat Compatible Kernel (RHCK). MongoDB does not support the Unbreakable Enterprise Kernel (UEK).|
|||MongoDB on-premises products released for RHEL version 8.0+ are compatible with and supported on Rocky Linux version 8.0+ and AlmaLinux version 8.0+, contingent upon those distributions meeting their obligation to deliver full RHEL compatibility.|
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Follow these steps to install MongoDB Community Edition using the
yum package manager.
/etc/yum.repos.d/mongodb-org-7.0.repo file so that
you can install MongoDB directly using
[mongodb-org-7.0] name=MongoDB Repository baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/7.0/x86_64/ gpgcheck=1 enabled=1 gpgkey=https://www.mongodb.org/static/pgp/server-7.0.asc
You can also download the
.rpm files directly from the
MongoDB repository. Downloads are organized by Red Hat / CentOS
7), then MongoDB
7.0), then architecture (e.g.
Prior to MongoDB 5.0, odd-numbered MongoDB release versions, such as
4.3, were development releases. Beginning with MongoDB 5.1,
MongoDB has quarterly rapid releases. For more information on the
differences between rapid and long-term support releases, see
To install the latest stable version of MongoDB, issue the following command:
sudo yum install -y mongodb-org
Alternatively, to install a specific release of MongoDB, specify each component package individually and append the version number to the package name, as in the following example:
sudo yum install -y mongodb-org-7.0.3 mongodb-org-database-7.0.3 mongodb-org-server-7.0.3 mongodb-mongosh-7.0.3 mongodb-org-mongos-7.0.3 mongodb-org-tools-7.0.3
yum automatically upgrades packages when newer versions
become available. If you want to prevent MongoDB upgrades, pin
the package by adding the following
exclude directive to
Most Unix-like operating systems limit the system resources that a
process may use. These limits may negatively impact MongoDB operation,
and should be adjusted. See UNIX
ulimit Settings for the recommended
settings for your platform.
Starting in MongoDB 4.4, a startup error is generated if the
ulimit value for number of open files is under
By default, MongoDB runs using the
mongod user account and
uses the following default directories:
/var/lib/mongo(the data directory)
/var/log/mongodb(the log directory)
The package manager creates the default directories during
installation. The owner and group name are
To use a data directory and/or log directory other than the default directories:
Create the new directory or directories.
Edit the configuration file
/etc/mongod.confand modify the following fields accordingly:
Ensure that the user running MongoDB has access to the directory or directories:
sudo chown -R mongod:mongod <directory>
If you change the user that runs the MongoDB process, you must give the new user access to these directories.
Configure SELinux if enforced. See Configure SELinux.
Starting in MongoDB 5.0, a new SELinux policy is available for MongoDB installations that:
Use default configuration settings.
Run on RHEL7 or later.
For MongoDB Enterprise installations that use LDAP authentication, the following additional SELinux policies must be in place:
For deployments that use LDAP authentication via OS libraries, MongoDB must have access to the
tcontext=system_u:object_r:ldap_port_t:s0LDAP ports. You can enable access by running
setsebool -P authlogin_nsswitch_use_ldap 1.
For deployments that use LDAP authentication via saslauthd, you must enable cluster mode by running
sudo setsebool -P daemons_enable_cluster_mode 1.
If your installation does not meet these requirements, refer to the
SELinux Instructions for
If your MongoDB deployment uses custom settings for any of the following:
You cannot use the MongoDB supplied SELinux policy. An alternative
is to create a custom SELinux policy, however an
improperly written custom policy may be less secure or may stop your
mongod instance from working.
Ensure you have the following packages installed:
sudo yum install git make checkpolicy policycoreutils selinux-policy-devel
Download the policy repository.
git clone https://github.com/mongodb/mongodb-selinux
Build the policy.
cd mongodb-selinux make
Apply the policy.
sudo make install
Starting in MongoDB 5.1, you must run the following command from the directory into which the SELinux policy was previously cloned before you can downgrade to an earlier MongoDB version:
sudo make uninstall
The SELinux policy is designed to work with the configuration that results from a standard MongoDB
.rpmpackage installation. See standard installation assumptions for more details.
The SELinux policy is designed for
mongodservers. It does not apply to other MongoDB daemons or tools such as:
The reference policy supplied by the SELinux Project includes a
mongodb_adminmacro. This macro is not included in the MongoDB SELinux policy. An administrator in the
unconfined_tdomain can manage
To uninstall the policy, go to the directory where you downloaded the policy repository and run:
sudo make uninstall
Follow these steps to run MongoDB Community Edition on your system. These instructions assume that you are using the default settings.
To run and manage your
mongod process, you will be using
your operating system's built-in init system. Recent versions of
Linux tend to use systemd (which uses the
while older versions of Linux tend to use System V init (which uses
If you are unsure which init system your platform uses, run the following command:
ps --no-headers -o comm 1
Then select the appropriate tab below based on the result:
systemd- select the systemd (systemctl) tab below.
init- select the System V Init (service) tab below.
To completely remove MongoDB from a system, you must remove the MongoDB applications themselves, the configuration files, and any directories containing data and logs. The following section guides you through the necessary steps.
This process will completely remove MongoDB, its configuration, and all databases. This process is not reversible, so ensure that all of your configuration and data is backed up before proceeding.
mongod process by issuing the following command:
sudo service mongod stop
By default, MongoDB launches with
bindIp set to
127.0.0.1, which binds to the localhost network interface. This
means that the
mongod can only accept connections from
clients that are running on the same machine. Remote clients will not be
able to connect to the
mongod, and the
not be able to initialize a replica set unless this value is set
to a valid network interface.
This value can be configured either:
MongoDB Community Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Contains the MongoDB Shell (