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 manually install MongoDB 7.0 Community
Edition on Amazon Linux using a downloaded
You can verify which Linux distribution you are running by running the following command on the command-line:
grep ^NAME /etc/*release
The result should be Amazon Linux or Amazon Linux AMI. If using a different Linux distribution, please see the install instructions for your platform.
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.
While MongoDB can be installed manually via a downloaded
tarball as described in this document, it is recommended to use the
yum package manager on your system to install MongoDB if
possible. Using a package manager automatically installs all needed
dependencies, provides an example
mongod.conf file to get you
started, and simplifies future upgrade and maintenance tasks.
➤ See Install MongoDB using the yum Package Manager for instructions.
MongoDB 7.0 Community Edition supports the following 64-bit Amazon Linux release on x86_64 architecture:
Amazon Linux 2023
Amazon Linux 2
MongoDB only supports the 64-bit versions of this platform.
MongoDB 7.0 Community Edition on Amazon Linux also supports the ARM64 architecture on select platforms.
See Platform Support for more information.
Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.
Use the following command to install the dependencies required for the
sudo yum install libcurl openssl xz-libs
Follow these steps to manually install MongoDB Community Edition from
After you have installed the required prerequisite packages, download
the MongoDB Community
tgz tarball from the following link:
In the Version dropdown, select the version of MongoDB to download.
In the Platform dropdown, select your operating system version and architecture.
In the Package dropdown, select tgz.
Using an archive manager program or the
tar command, extract the
files. For example, to extract from the terminal shell, you can use the
If you downloaded a different MongoDB 7.0 point release,
be sure to modify the command to reflect the correct
tar -zxvf mongodb-linux-x86_64-*-7.0.3.tgz
The MongoDB binaries are in the
directory. To avoid having to specify the path to the MongoDB
binaries, add the contents of the
<mongodb-install-directory>/bin/ directory to a directory in the
$PATH such as
/usr/bin/. For example, you can either:
Copy the binaries into
sudo cp <mongodb-install-directory>/bin/* /usr/bin/
Create symbolic links to each of these binaries to
sudo ln -s /full/path/to/<mongodb-install-directory>/bin/* /usr/bin/
/full/path/towith the full path to the extracted directory contents.
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, a MongoDB instance stores:
its data files in
its log files in
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> or
sudo mkdir -p
<directory> depending on the user that will run MongoDB. (See your
linux man pages for information on
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
directories to give this user access to these directories.
To specify a different log file directory and data file directory, edit
storage.dbPath settings in
/etc/mongod.conf. Ensure that the user running MongoDB has
access to these directories.
Follow these steps to run MongoDB Community Edition. These instructions assume that you are using the default settings.
Create a directory where the MongoDB instance stores its data. For example:
sudo mkdir -p /var/lib/mongo
Create a directory where the MongoDB instance stores its log. For example:
sudo mkdir -p /var/log/mongodb
The user that starts the MongoDB process must have read and write permission to these directories. For example, if you intend to run MongoDB as yourself:
sudo chown `whoami` /var/lib/mongo # Or substitute another user sudo chown `whoami` /var/log/mongodb # Or substitute another user
Verify that MongoDB has started successfully by
checking the process output for the following line in the
[initandlisten] waiting for connections on port 27017
You may see non-critical warnings in the process output. As long as you see the log line shown above, you can safely ignore these warnings during your initial evaluation of MongoDB.
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 which is accessible from the remote clients.
This value can be configured either: