MongoDB is a highly-scalable NoSQL database with a document-based data model and an expressive query language. DigitalOcean’s MongoDB One-Click application lets you create a Droplet with MongoDB pre-installed to help get your application off the ground quickly.
In addition to the package installation, the One-Click also:
22, rate limited), HTTP (port
80), and HTTPS (port
After the MongoDB One-Click Droplet is created:
The MongoDB instance is available at
127.0.0.1:27017 and is bound to
localhost by default. Note that UFW does not allow
27017 by default.
MongoDB’s configuration details are in
In addition, there are a few customized setup steps that we recommend you take.
Once the Droplet is created, you can SSH to the server as
root. Make sure to substitute the Droplet’s IP address.
Then you can connect to the test database with the MongoDB shell.
When you connect, you’ll see several startup warnings before you receive the MongoDB shell prompt:
Server has startup warnings: 2018-09-12T19:10:18.867+0000 I STORAGE [initandlisten] 2018-09-12T19:10:18.867+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine 2018-09-12T19:10:18.867+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem 2018-09-12T19:10:19.637+0000 I CONTROL [initandlisten] 2018-09-12T19:10:19.637+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database. 2018-09-12T19:10:19.637+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted. 2018-09-12T19:10:19.637+0000 I CONTROL [initandlisten]
To resolve the
STORAGE warning, you can set the storage engine to WiredTiger. WiredTiger is the default storage engine in modern versions of MongoDB (3.2+).
CONTROL warning about unrestricted read/write access to the database and configuration means that any user logged into the Droplet will have access to the database and configuration until you set up access controls. However, remote access is blocked in two ways: MongoDB is bound to the local interface, so it doesn’t listen to requests from outside the local machine, and UFW is additionally configured to block port 27017, which MongoDB binds to.
You can also access your MongoDB instance remotely via an SSH tunnel using:
ssh -L 4321:localhost:27017 use_your_username@use_your_droplet_ip -f -N mongo --port 4321
This opens an SSH connection which allows you to access port 27017 of the remote server locally on port 4321. This can be useful for securely accessing your MongoDB instance without opening it up to accept connections via the wider internet.
In order to enable access over the internet, you need to modify the value of
/etc/mongod.conf. However, before doing so, make sure to review the security checklist from the MongoDB documentation. In addition to enabling one of the forms of authentication supported by MongoDB, if you open a port to allow connection from the internet, you should also configure the firewall so that it only allows remote connections from specific IP addresses.
To run MongoDB in production, there are several additional steps you should take, including: