Self-Hosted MongoDB
Learn how to optimize your DB cost? This article will help you with the complete migration steps from a cloud to a self-hosted environment.
You’re probably hosting your MongoDB on a reliable cloud service provider say Atlas for instance because you really want to focus on your idea and delegate all the subtle key management areas such as networking, storage, access, etc.
It all looks good initially until your small idea starts turning into a business and the cost starts skyrocketing. Even if that is not the case, this post will still give you a general overview of the technical complexities involved (and bucks saved!) if you were to migrate to a self-hosted solution.
BTW, how much savings are we talking about? Let’s do a quick comparison between an Atlas instance and a self-hosted MongoDB on AWS.
Atlas (~$166/month)
$0.23/hour based on the above-selected requirements (~ cloud.mongodb.com)
AWS (~$36/month)
$0.0416/hour for the instance and additional pricing based on the EBS type and storage (~ calculator.aws)
It is almost 4.5x savings just in terms of the infrastructure!
Now that you know the major why(s) and are still reading this post, without further ado, let’s dive into the tech.
Outline
- Setting up the infrastructure
- Setting up MongoDB
- Bulk migration
- Delta-sync to bridge the connection switch latency (not applicable to stale clusters)
Since the entire content can be a bit exhausting in one place, I’m going to divide this into 2 related posts.
1. Setting up the Infrastructure
I’m going to mention below the guide for setting up an instance running RedHat Enterprise Linux 8 on AWS. This is because MongoDB generally performs better with the xfs file-system.
Spin up an EC2 Instance
I’ve used a instance that comes with 2 vCPUs and 2Gb of RAM albeit you can select any instance of your choice.
It is recommended that your DB should have access to at least 1GB of RAM and 2 real cores as that directly affects the performance during caching & concurrency mechanisms as handled by the default engine WiredTiger. You can read more about the production notes related to the RAM and CPU requirements here.
Configuration Overview:
- OS: Redhat Enterprise Linux 8 (x64 intel-based)
- Instance Type: t3.small
- Storage: 10GB(os) + 30GB(data) + 3GB(logs) of EBS i.e. 3 separate volumes
I’m assuming that you’re familiar with creating a VM on AWS.
Now, once the instance is in running state, assign an Elastic IP to it and then simply do a remote login into the machine.
We'll need the Elastic IP to setup public hostname for the instance
Mount Additional Volumes
We have added 2 additional EBS volumes other than the Root FS for Data and Logs which are yet to be mounted (Remember the 30Gb and 3Gb?). You can list the volume blocks using,
The additional volumes will be listed right after the root block (refer to the arrows)
In the image above, you can see that the additional volumes are named
- xvdb (30Gb space to store data)
- xvdc (3Gb space to store logs)
Now, let’s create the file-systems in those volumes.
is an alias option for setting the volume label
And then mount the volumes.
In order for these changes to reflect, the system must be rebooted. Hence, now we also need the partition persistence so that in case of an unintentional reboot we don’t lose the Database storage.
We can achieve this by specifying the mount rules in the fstab file. You can read more about it here.
Before that let's copy the UUID of the above partitions(because they are unique and won't change over a system restart)
Copy the UUIDs listed for /dev/xvdb and /dev/xvdc. Refer to the “LABEL” for block identification
Now open the file and paste the configuration in the following format.
Update Hostname
The hostname will be used to identify your database server on the network. You can either use the above assigned Elastic IP or Domain name (if available). Open the file and append the entry. For e.g.
Update the Process Limits (Optional)
This is optionally required in order to control the maximum number of acceptable connections while keeping the system stable. Open the file and add the following entries.
Now that all of the infra related prerequisites are sorted, reboot the instance, and let’s proceed to MongoDB installation.
1. Setting up MongoDB
Add the Repo Source
Create a file and add the following package repository details.
Now let’s install MongoDB.
Create directories and setup permissions
MongoDB by default uses the following paths to store the data and the internal logs:
/var/lib/mongo → Data/var/log/mongodb → Logs
Create the directories
Change user & group permissions
Create an Admin User
The mongod daemon/service must be first running before we proceed to create a user. Let’s use the default config(stored in ) for now and start the daemon process.
The above command will start the mongod daemon in fork mode (default).
Now, let’s login to the server and create our first admin user.
Open a mongo shell
Use the "admin" database to create the root-admin
Create the admin user
Create a regular user
Shutdown the server for now. We'll restart again with the modified config
Setting up Authentication
Here, we’ll enable the database authentication and modify the bind-address for our server to be accessible in the public domain. Open and make the below changes.
Save the config and restart the server.
Test Login
You can verify if the credentials work using,
That is it about the initial setup! Please stay tuned for my next related post on the detailed migration process and tips on keeping the DB production-ready.
P.S. Thanks to Piyush Kumar for helping curate this post!
