MongoDB Atlas, the managed MongoDB service, now allows you to pause and restart your database clusters. This makes it easy and affordable for you to integrate MongoDB into DevOps workflows where always-on access to the underlying data is not required — e.g. development or testing.
When combined with Atlas’s fully managed backup service, this new functionality allows you to seamlessly create multiple environments for development and testing while keeping infrastructure and operational costs to a minimum.
For example, you could restore a subset of your production data (using queryable snapshots) to a smaller database to try out new features introduced in MongoDB 3.6. You can even restore to different Atlas Projects, regions, or clouds to give different members of your organization local access. And now with the pause cluster feature, your development and testing teams can easily stop any databases when they’re not being used.
Pausing and resuming a cluster requires just a few clicks in the Atlas UI or a single call with the Atlas API. When the cluster is paused, you are charged for provisioned storage and any associated backups, but not for compute instance hours associated with your Atlas cluster. Clusters can be paused for up to 7 days. If you do not resume a paused cluster within the 7 day window, Atlas will automatically resume the cluster.
The pause/resume feature is now available for all dedicated instance sizes (M10 and above) in every supported region on AWS, Microsoft Azure, and Google Cloud Platform.
Larger Max Instance Size on AWS (M200)
MongoDB Atlas now supports a larger instance size on Amazon Web Services. The new M200 clusters are designed for the most demanding production workloads and peak hours of activity. Each instance features 64 vCPUs, 256 GB of RAM, and 1500 GB of storage included, with 25 Gigabit network connectivity.
M200 instances are available in all 14 AWS regions supported by MongoDB Atlas.
Not an Atlas user yet? Get started with a 512MB database for free.