We’re very excited to announce $15 Shared Cluster plans across all major cloud providers (AWS, Azure, Google, et al.) on MongoLab! MongoDB replica set clusters offer many benefits to developers, the biggest being high-availability. Any application in production needs a highly-available database to minimize downtime. At $15/GB per month, weekend hackers and teams on a tight budget can now afford to rest easy knowing that their application is backed by a highly-available MongoLab database. Continue Reading →
MongoLab runs all of its hosted MongoDB deployments with authorization enabled, which means that username / password authentication is required before your database can be accessed.
For lower-level network security we also allow you to configure custom firewall settings. This feature is available to all MongoLab users on Dedicated plans.
Configuring custom firewalls
If you have yet to configure a custom firewall, you’ll notice a new Firewall tab from your deployment view. By default, your firewall configuration will include 0.0.0.0/0, which allows all traffic to your database.
To lock down your deployment, we allow three options for configuring new firewall rules. You may:
- Whitelist IP addresses
- Whitelist Amazon EC2 Security Groups
- Copy existing rules from one deployment to another
Whitelisting IP addresses
MongoLab can configure your firewall to limit access to only the IP address(es) (or address ranges) you specify. We use CIDR rules to define the allowable address(es) and secure access to your MongoLab-hosted Dedicated plan databases.
Whitelisting Amazon EC2 security groups (AWS only)
If your Dedicated plan database is hosted on AWS and your application is running from the same AWS region and on EC2-Classic, we recommend allowing access to Security Group(s) instead of IP addresses. This way you won’t need to change your database deployment’s firewall rules as you spin up/down your app servers.
To control access to your MongoLab-hosted database using your EC2 security group, you’ll need to provide your AWS account ID (a 12-digit number) and the name or ID of your Security Group(s).
Copy existing rules
If you have already configured custom allow rules for one MongoDB deployment in your MongoLab account, you can copy these rules to any other Dedicated plan deployment in your account. Simply select which deployment you want to copy from, and we’ll take care of the rest!
Security is our priority
MongoLab takes the security of MongoLab accounts and deployments seriously. We are continuously working to improve the features and tools that increase the safety of your data. To find up-to-date information on what security features are available to MongoLab users, visit our documentation portal. As always, if you have any questions or feedback you can reach us at firstname.lastname@example.org.
MongoDB offers new geospatial features in versions 2.4 and 2.6. The core of these features is the introduction of GeoJSON, an open-source format for rich geospatial types that go beyond what MongoDB has supported in previous versions.
This post is a primer for developers new to geospatial data in MongoDB. We aim to familiarize you with geospatial fundamentals in MongoDB and help you get the most out of your data.
A few months ago, we wrote a blog post on finding and terminating long-running operations in MongoDB. To help make it even easier for MongoLab users* to quickly identify the cause behind database unresponsiveness, we’ve integrated the currentOp() and killOp() methods into our management portal. Continue Reading →
We’re excited to announce the next generation of MongoLab’s production-ready Dedicated plans on Amazon Web Services (AWS). After years of experience managing a fleet of over a hundred thousand MongoDB databases ranging from tiny to terabytes, we’ve seen a large number of use cases. We know that when it comes to databases, one size doesn’t fit all.
That’s why our new 100% SSD-backed Dedicated plans on AWS offer a much larger variety than our previous generation. We have analyzed thousands of existing deployments and created packages that allow users to choose what is important for their particular use case. These new plans give users the power to optimize for cost efficiency, storage, or performance. Continue Reading →
Updated September 12, 2014: Added section on compatibility with 2.6
Ever since Meteor 0.7.0 first introduced oplog tailing, we’ve had a lot of users asking us about using the MongoDB oplog with their Meteor applications. As a result, we thought a step-by-step tutorial would help folks get started.
Closely approaching the one year mark of when I first joined MongoLab (and the MongoDB community), I had the pleasure of attending the inaugural MongoDB World conference put together by the incredible MongoDB team. Second only to the excitement around major MongoDB feature announcements was the collective disbelief that this was MongoDB’s first multi-day conference ever. A big congratulations to all those that worked hard to put on such a massive (did you see the Intrepid!?) event. All this planning would have been for naught if MongoDB leaders and engineers failed to deliver announcements and features that would meet and exceed expectations. From major public cloud announcements to the reveal of document-level locking in version 2.8, developers and conference goers had plenty to be excited about. There was a lot to digest from the conference… we’ll cover the major highlights in case you missed them. Continue Reading →
Great news, Google Cloud users!
Today Google, MongoDB Inc., and MongoLab are announcing the arrival of fully-managed, production-ready MongoDB replica set plans on the Google Cloud Platform (GCP). These plans are hosted on Google Compute Engine (GCE) and managed by MongoLab. You can get started for free!
By leveraging MongoLab’s MongoDB-as-a-Service platform on GCP, Google developers running MongoDB can focus on product development and not get bogged down by database administration and operations. Automated provisioning, multi-zone data replication, backups and monitoring are all provided by the platform, so developers only need to worry about is their schema and their code (ok, we can help you a little with that too). Continue Reading →