MongoDB Atlas Compute Autoscaling Now In Public Beta

Jenny Liang
October 1, 2019 | Updated: March 17, 2020
#scaling

Update: Autoscaling is now GA for all dedicated clusters in MongoDB Atlas

You can now opt in to our compute auto-scaling open beta for any dedicated cluster (M10 and higher) on MongoDB Atlas. When enabled, Atlas will track key resource utilization metrics in real-time and adjust your cluster size up or down as needed, using predictive modeling and proven practices developed from managing tens of thousands of MongoDB deployments.

Predictive Resource Modeling

The open beta for compute auto-scaling is based on a predictive model that uses heuristics from managing numerous MongoDB deployments. Specifically, Atlas will examine two key resource utilization metrics—CPU and memory—every five minutes and determine whether a scaling event is necessary based on certain thresholds. For upscaling events, Atlas will look at the average utilization of each metric over the past hour. For downscaling events, Atlas will track the maximum utilization for both metrics over the past 72 hours. In future iterations, we will improve the algorithm to be more sophisticated and responsive to changes in workload.

Optimize Capacity Management

You can enable compute auto-scaling through either the UI or the public API. Auto-scaling is available on all clusters M10 and higher on Azure and GCP, and on all "General" class clusters M10 and higher on AWS. To enable auto-scaling from the UI, select the Auto-scale “Cluster tier” option and choose a maximum cluster size from the available options.

Auto-scaling in Atlas

You can also opt in to automated downscaling, which will require you to also select a minimum cluster size. Opting into downscaling allows you to intelligently save on costs by downsizing your database during periods of low traffic or load.

At this time, compute auto-scaling is not supported by clusters on the M0, M2, or M5 tiers, sharded clusters, clusters with low-CPU or NVMe storage, or clusters with IOPS provisioned.

Set And Forget It

Scaling cluster sizes in Atlas is already fairly easy with the UI or API, but compute auto-scaling takes it one step further and automates the actual operation without any manual intervention required. This is especially useful for developers and DevOps engineers who frequently need to adjust the cluster size to accommodate changes in workload. While the beta feature is currently not suitable for applications that experience sudden spikes, it’s a great fit for those that have regular scaling events, seasonal business patterns, or anticipate steady growth over time.

Tracking the updates in the Activity Tracker

Atlas automatically applies updates to your cluster in a rolling fashion so there’s no impact to your application. You’ll also receive an email notification any time your cluster has successfully scaled up or down, and you can review all automated scaling operations in your project’s activity feed in the Atlas UI.

An Autonomous Cloud Database

Whether you’re building a new application or supporting an existing one, Atlas helps automate the time-consuming administration tasks so you can free up time to focus on development. Together with other features like storage auto-scaling, self-healing clusters, and automated patches and bug fixes, the new compute auto-scaling makes it easier than ever to run your database in the cloud.

Questions or feedback on the compute auto-scaling open beta in Atlas? Let us know here.


← Previous

Stitch Hosting: A Drag-and-Drop Delight

Speed your static hosting uploads with Stitch's enhanced drag and drop feature.

September 30, 2019
Next →

Security in Government Solutions: Why Secure By Default is Essential

Data security in government agencies is table stakes at this point. Everyone knows it’s essential, both for compliance and data protection purposes. However, most government agencies are working with solutions that require frequent security patches or built-on tools to protect their data. Today, the federal government is pushing its agencies to move to modernize their solutions and improve their security posture. For example, the DHS and Cybersecurity and Infrastructure Security Agency’s recently issued technical rule for modernization of the Protected Critical Information Infrastructure program – a program that provides legal protections for cyber and physical infrastructure information submitted to DHS. “The PCII Program is essential to CISA’s ability to gather information about risks facing critical infrastructure,” said Dr. David Mussington, Executive Assistant Director for Infrastructure Security. “This technical rule modernizes and clarifies important aspects of the Program, making it easier for our partners to share information with DHS. These revisions further demonstrate our commitment to ensuring that sensitive, proprietary information shared with CISA remains secure and protected.” So how can government agencies modernize their data infrastructure and find solutions that not only protect data but also power innovation? Let’s look into a few different strategies. 1. Why secure by default is key Secure by default means that any piece of software uses default security settings that are configured for the highest possible security out of the box. CISA Director Jen Easterly has addressed how using solutions that are secure by default is critical for any organization. “We have to have [multi-factor authentication] by default. We can't charge extra for security logging and [single sign-on],” Easterly said . “We need to ensure that we're coming together to really protect the technology ecosystem instead of putting the burden on those least able to defend themselves.” “The American people have accepted the fact that they’re constantly going to have to update their software,” she said. “The burden is placed on you as the user and that’s what we have to collectively stop.” Easterly is right. Secure-by-design solutions are vital to the success of data protection. The expectation should alway be that solutions have built-in, not bolt-on security features. One approach that’s gaining traction both in the public and private sectors is zero trust environments. In a zero trust environment, the perimeter is assumed to have been breached. There are no trusted users, and no user or device gains trust simply because of its physical or network location. Every user, device, and connection must be continually verified and audited. As the creator of zero trust, security expert John Kindervag, summed it up: “Never trust, always verify.” For government agencies, that means the underlying database must be secure by default, and it needs to limit users’ opportunities to make it less secure. 2. Security isn't just on-prem anymore; cloud is secure, too Cloud can be a scary word for public sector organizations. Trusting your sensitive data to the cloud might feel risky for those who handle some of the country’s most sensitive data. But, cloud providers are stepping up to meet the security needs of government agencies. There is no need to fear the cloud anymore. Government agencies and other public sector organizations nationwide are navigating cloud modernization through the lens of increased cybersecurity requirements outlined in the 2021 Executive Order on Improving the Nation’s Cybersecurity . “The Federal Government must adopt security best practices; advance toward Zero Trust Architecture; accelerate movement to secure cloud services, including Software as a Service (SaaS), Infrastructure as a Service (IaaS), and Platform as a Service (PaaS); centralize and streamline access to cybersecurity data to drive analytics for identifying and managing cybersecurity risks; and invest in both technology and personnel to match these modernization goals.” Also, the major cloud providers are well established, purpose-built options for government users. AWS GovCloud, for example, is more than a decade old and was “ the first cloud provider to build cloud infrastructure specifically designed to meet U.S. government security and compliance needs.” This push by the federal government toward cloud modernization and increased cybersecurity will be a catalyst in upcoming years for rapid cloud adoption and greater dependence on cloud solutions designed specifically for government users. 3. Security features purpose-built for goverment needs are essential Government agencies are held to a higher standard than those in the private sector. From data used in sometimes life-or-death missions to data for students building their futures in educational institutions (and everything in between), security has real-world consequences. Today, security is non-negotiable and like we explored above, it’s especially crucial that public sector entities have built-in security measures to keep data protected. So, what built-in features should you look for? Network isolation and access It’s critical that your data and underlying systems are fully isolated from other organizations using the same cloud provider. Database resources should be associated with a user group, which is contained in its own Virtual Private Cloud (VPC), and access should be granted by IP access lists, VPC peering, or private endpoints. Encyption in flight, at rest, and in use Encryption should be the standard. For example, when using MongoDB Atlas, all network traffic is encrypted using Transport Layer Security (TLS). Encryption for data at rest is automated using encrypted storage volumes. Customers can use field-level encryption to encrypt sensitive workloads which enables you to encrypt data in your application before you send it over the network to MongoDB clusters. Users can bring their own encryption keys for an additional level of control. Granular database auditing Granular database auditing allows administrators to answer detailed questions about systems activity by tracking all commands against the database. This ensures you always know who has access to what data and how they’re using it. Multi-factor authentication User credentials should always be stored using industry-standard and audited one-way hashing mechanisms, with multi-factor authentication options including SMS, voice call, a multi-factor app, or a multi-factor device, ensuring only approved users have access to your data. MongoDB Atlas for Government: Purpose-built for public sector As we’ve discussed, solutions that are purpose-built with built-in security are ideal for government agencies, and choosing the right one is the best way to keep sensitive data protected. MongoDB Atlas for Government on AWS GovCloud recently secured its FedRAMP Moderate authorization thanks to these security measures built into the solution. FedRAMP is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. To ensure the utmost levels of security, Atlas for Government is an independent, dedicated environment for the U.S. public sector, as well as ISVs looking to build U.S. public sector offerings. Public Sector organizations carry a heavy burden when it comes to keeping data protected. However, with the right data platform underpinning modern applications – a platform with built-in security features – progress doesn’t mean you have to compromise on security. Want to learn more about data protection best practices for public sector organizations? Attend our upcoming webinar on April 12 for deeper insight .

March 28, 2023