- Install MongoDB >
- Install MongoDB Enterprise >
- Install MongoDB Enterprise on Linux >
- Install MongoDB Enterprise Edition on Amazon Linux
Install MongoDB Enterprise Edition on Amazon Linux¶
On this page
Important
MongoDB 5.3 binaries are currently available only as release candidates. Release candidates can be used for early testing of new features, but are not suitable for production deployments.
This version of the manual is for an upcoming release and is currently a work in progress.
Overview¶
Use this tutorial to install MongoDB 5.0 Enterprise Edition
on Amazon Linux using the yum
package manager.
MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.
Verify Linux Distribution¶
You can verify which Linux distribution you are running by running the following command on the command-line:
The result should be Amazon Linux or Amazon Linux AMI. If using a different Linux distribution, please see the install instructions for your platform.
MongoDB Version¶
This tutorial installs MongoDB 5.0 Enterprise Edition. To install a different version of MongoDB Enterprise, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.
Considerations¶
Platform Support¶
MongoDB 5.0 Enterprise Edition supports the following :red:`64-bit` Amazon Linux release on x86_64 architecture:
- Amazon Linux 2
MongoDB only supports the 64-bit versions of this platform.
MongoDB 5.0 Enterprise Edition on Amazon Linux also supports the ARM64 architecture on select platforms.
See prod-notes-supported-platforms for more information.
Production Notes¶
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Install MongoDB Enterprise Edition¶
Follow these steps to install MongoDB Enterprise Edition using the
yum
package manager. Select the tab for your version of
Amazon Linux:
- Amazon Linux 2
- Amazon Linux (2013.03+)
Configure repository.¶
Create an /etc/yum.repos.d/mongodb-enterprise-5.0.repo
file so that
you can install MongoDB enterprise directly using yum
:
Note
If you have a mongodb-enterprise.repo
file
in this directory from a previous installation of MongoDB, you
should remove it. Use the mongodb-enterprise-5.0.repo
file above to install MongoDB 5.0.
You can also download the .rpm
files directly from the
MongoDB repository. Downloads are organized by Amazon Linux
version (e.g. 2
), then MongoDB
release version
(e.g. 5.0
), then architecture (e.g. x86_64
).
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
MongoDB Versioning.
Install the MongoDB Enterprise packages.¶
Install MongoDB Enterprise .¶
Issue the following command:
Install a specific release of MongoDB Enterprise.¶
To install a specific release, you must specify each component package individually along with the version number, as in the following example:
If you only install mongodb-enterprise=5.0.0
and do not include the
component packages, the latest version of each MongoDB package will be
installed regardless of what version you specified.
Pin a specific version of MongoDB Enterprise.¶
Although you can specify any available version of MongoDB
Enterprise, yum
upgrades the packages when a newer
version becomes available. To prevent unintended upgrades, pin
the package by adding the following exclude
directive to your
/etc/yum.conf
file:
Configure repository.¶
Create an /etc/yum.repos.d/mongodb-enterprise-5.0.repo
file so that
you can install MongoDB enterprise directly using yum
:
Note
If you have a mongodb-enterprise.repo
file
in this directory from a previous installation of MongoDB, you
should remove it. Use the mongodb-enterprise-5.0.repo
file above to install MongoDB 5.0.
You can also download the .rpm
files directly from the
MongoDB repository. Downloads are organized by Amazon Linux
version (e.g. 2013.03
), then MongoDB
release version
(e.g. 5.0
), then architecture (e.g. x86_64
).
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
MongoDB Versioning.
Install the MongoDB Enterprise packages.¶
Install MongoDB Enterprise .¶
Issue the following command:
Install a specific release of MongoDB Enterprise.¶
To install a specific release, you must specify each component package individually along with the version number, as in the following example:
If you only install mongodb-enterprise=5.0.0
and do not include the
component packages, the latest version of each MongoDB package will be
installed regardless of what version you specified.
Pin a specific version of MongoDB Enterprise.¶
Although you can specify any available version of MongoDB
Enterprise, yum
upgrades the packages when a newer
version becomes available. To prevent unintended upgrades, pin
the package by adding the following exclude
directive to your
/etc/yum.conf
file:
Run MongoDB Enterprise Edition¶
- ulimit Considerations
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.
Note
Starting in MongoDB 4.4, a startup error is generated if the
ulimit
value for number of open files is under64000
.
- Directories
By default, a MongoDB instance stores:
- its data files in
/var/lib/mongo
- its log files in
/var/log/mongodb
If you installed via the package manager, these default directories are created during the installation.
If you installed manually by downloading the tarballs, you can create the directories using
mkdir -p <directory>
orsudo mkdir -p <directory>
depending on the user that will run MongoDB. (See your linux man pages for information onmkdir
andsudo
.)By default, MongoDB runs using the
mongod
user account. If you change the user that runs the MongoDB process, you must also modify the permission to the/var/lib/mongo
and/var/log/mongodb
directories to give this user access to these directories.To specify a different log file directory and data file directory, edit the
systemLog.path
andstorage.dbPath
settings in the/etc/mongod.conf
. Ensure that the user running MongoDB has access to these directories.- its data files in
Procedure¶
Follow these steps to run MongoDB Enterprise Edition. These instructions assume that you are using the default settings.
Init System
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 systemctl
command),
while older versions of Linux tend to use System V init (which uses
the service
command).
If you are unsure which init system your platform uses, run the following command:
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.
- systemd (systemctl)
- System V Init (service)
Start MongoDB.¶
You can start the mongod
process by issuing the
following command:
If you receive an error similar to the following when starting
mongod
:
Failed to start mongod.service: Unit mongod.service not found.
Run the following command first:
Then run the start command above again.
Verify that MongoDB has started successfully.¶
You can verify that the mongod
process has started
successfully by issuing the following command:
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
Stop MongoDB.¶
As needed, you can stop the mongod
process by issuing the
following command:
Restart MongoDB.¶
You can restart the mongod
process by issuing the following
command:
You can follow the state of the process for errors or important messages
by watching the output in the /var/log/mongodb/mongod.log
file.
Begin using MongoDB.¶
Start a mongosh
session on the same host machine as the
mongod
. You can run mongosh
without any command-line options to connect to a
mongod
that is running on your localhost with default
port 27017.
For more information on connecting using mongosh
,
such as to connect to a mongod
instance running
on a different host and/or port, see the
mongosh documentation.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
Start MongoDB.¶
You can start the mongod
process by issuing the following
command:
Verify that MongoDB has started successfully¶
You can verify that the mongod
process has started
successfully by checking the contents of the log file at
/var/log/mongodb/mongod.log
for a line reading
where <port>
is the port configured in /etc/mongod.conf
, 27017
by default.
You can optionally ensure that MongoDB will start following a system reboot by issuing the following command:
Stop MongoDB.¶
As needed, you can stop the mongod
process by issuing the
following command:
Restart MongoDB.¶
You can restart the mongod
process by issuing the following
command:
You can follow the state of the process for errors or important messages
by watching the output in the /var/log/mongodb/mongod.log
file.
Begin using MongoDB.¶
Start a mongosh
session on the same host machine as the
mongod
. You can run mongosh
without any command-line options to connect to a
mongod
that is running on your localhost with default
port 27017.
For more information on connecting using mongosh
,
such as to connect to a mongod
instance running
on a different host and/or port, see the
mongosh documentation.
To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. For the driver documentation, see Start Developing with MongoDB.
Uninstall MongoDB¶
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.
Warning
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.
Stop MongoDB.¶
Stop the mongod
process by issuing the following command:
Remove Packages.¶
Remove any MongoDB packages that you had previously installed.
Remove Data Directories.¶
Remove MongoDB databases and log files.
Additional Information¶
Localhost Binding by Default¶
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 mongod
will
not be able to initialize a replica set unless this value is set
to a valid network interface.
This value can be configured either:
Warning
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.
For more information on configuring bindIp
, see
IP Binding.
MongoDB Enterprise Edition Packages¶
MongoDB Enterprise Edition is available from its own dedicated repository, and contains the following officially-supported packages:
Package Name | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
mongodb-enterprise |
A metapackage that automatically installs the component
packages listed below. |
||||||||
mongodb-enterprise-database |
A
|
||||||||
-mongosh |
Contains the MongoDB Shell (mongosh ). |
||||||||
mongodb-enterprise-tools |
A
|