Install MongoDB Community on Amazon Linux using .tgz Tarball
On this page
Use this tutorial to manually install MongoDB 3.6 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 AMI . If using a different Linux distribution, please see the install instructions for your platform.
This tutorial installs MongoDB 3.6 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
.tgz 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 3.6 Community Edition supports the following 64-bit Amazon Linux release on x86_64 architecture:
- Amazon Linux (2013.03 or later)
MongoDB only supports the 64-bit version of this platform.
See Supported Platforms 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 MongoDB Community
sudo yum install libcurl openssl
Follow these steps to manually install MongoDB Community Edition from the
Download the tarball for your system from the MongoDB Download Center. Ensure you select the correct version of Amazon Linux for the host machine.
Using an archive manager program or the
tar command, extract the files. For example, to extract from the terminal shell, you can use the following
If you downloaded a different MongoDB 3.6 point release, be sure to modify the command to reflect the correct
.tgz file name.
tar -zxvf mongodb-linux-x86_64-*-3.6.19.tgz
The MongoDB binaries are in the
<mongodb-install-directory>/bin 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/to with the full path to the extracted directory contents.
- Most Unix-like operating systems limit the system resources that a session may use. These limits may negatively impact MongoDB operation. See UNIX ulimit Settings for more information.
- By default, 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
/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 and storage.dbPath settings in the
/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
To run MongoDB, run the mongod process at the system prompt.
mongod --dbpath /var/lib/mongo --logpath /var/log/mongodb/mongod.log --fork
Verify that MongoDB has started successfully by checking the process output for the following line in the log file
[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.
Start a mongo shell on the same host machine as the mongod. You can run the mongo shell without any command-line options to connect to a mongod that is running on your localhost with default port 27017:
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: