Atlas Changelog¶

On this page

2019 Releases¶

Supports the following Azure regions:
- Germany West Central
- Switzerland North
Supports M0 Free Tier and M2/M5 shared starter clusters in the GCP Brazil (São Paulo) region.
Supports M0 Free Tier clusters in the AWS Syndey region.
Enables faster restores from Cloud Provider Snapshot backups.

Introduces compute auto-scaling in public beta.
Enhances Integrations interface for third party services.
Introduces EU destinations for DataDog and Opsgenie integrations.
Supports the official Terraform MongoDB Atlas Provider .
Supports the MongoDB Atlas Open Service Broker for Kubernetes.
Introduces Point-in-Time Restore (PITR) available for clusters using AWS Cloud Provider Snapshots.
Increases throughput for M2 & M5 cluster tiers.

Introduces the Query Profiler for M10+ clusters.
Newly deployed MongoDB Atlas clusters in the following Azure regions will be spread across availability zones:
- Central US
- East US
- East US 2
- West US 2
- France Central
- North Europe
- UK South
- West Europe
- Japan East
- Southeast Asia
Pre-existing clusters, and clusters in all other Azure other regions will continue to be deployed in Availability Sets.
Internal Stitch/Charts-created database users and IP whitelist entries no longer show in the Atlas UI.
MongoDB Cloud billing authenticates credit cards for customers in the European Economic Area in compliance with the second Payment Services Directive (PSD2). To learn more about Strong Customer Authentication, see Strong Customer Authentication (SCA) Changes.
Enables always-on database-level authentication access auditing for dedicated clusters.

Supports the AWS Bahrain region.
Changes the preferred region in a multi-region cluster without requiring a rolling resync.
Adds key-value pair labels to cluster resources in the Public API.

Supports the Azure United Arab Emirates North region.
Introduces M80 general class cluster tier on AWS offering next-gen infrastructure. This replaces the more expensive M100.
Removes M100 cluster tier on AWS as an option for new cluster deployments.
Disables the ability to create new Personal API Keys. These keys are deprecated. Use Programmatic API Keys to access the Cloud Manager API.

Enables free daily backups for M2 and M5 clusters.
Unifies the login experience: accounts for MongoDB Cloud, Support, and JIRA use the same credentials.
Adds new project-level role Project Cluster Manager. This role allows operators to scale clusters but not allow those operators to:
- Terminate clusters,
- Change the security configuration changes, or
- Access data.
Allows deploy single-shard sharded clusters in Atlas.

Supports MongoDB 4.2.
Supports $searchBeta.
- Includes Memory, CPU, and Disk Usage monitoring. For more information, see Performance Considerations.
- Includes alerts for Memory.
- Requires MongoDB 4.2.
Introduces Atlas Data Lake on-demand query service.
Supports Cloud Provider Snapshots for 4.2 replica sets.
Supports Encryption at Rest for snapshots.
Added Aggregation Pipeline Builder to the Data Explorer.

Support for GCP Osaka region.
Support to search for organization or project names that are one character long.

Cloud Provider Snapshots are now available for GCP-backed clusters.
Atlas clusters can now use Google Cloud KMS for encryption at rest.
Atlas clusters now have a new MongoDB configuration option that allows agents to continue connecting even if you have exceeded the maximum number of connections. For example, this means that Atlas continues to gather monitoring data after reaching the maximum number of connections. This change affects all new Atlas clusters. Existing Atlas clusters are affected the next time you request a configuration change to a cluster.
Atlas projects may now use either the Continuous Backup or the Cloud Provider Snapshots backup method. An Atlas project supports multiple backup types among clusters within that project. You must terminate the existing backup method before switching between backup methods for an Atlas cluster.
Enhanced left-hand navigation.

Atlas clusters can re-use public IP addresses when replaced in the same region.
Can configure backup schedule and retention for Snapshots Backup.
AWS EC2 Capacity for all cluster tiers in all regions and availability zones is visible via the Atlas Admin UI.

UX improvements to the cluster Connect modal.
Most server replacements get initial data from a disk snapshot of the primary instead of an initial sync.
Support for new shared tier regions:
- AWS
  - eu-central-1 (M2/M5)
  - eu-west-1 (M0)
  - us-west-2 (M0)
- Azure
  - northeurope (M0)
  - westus (M0/M2/M5)
Cloud Provider Snapshots for Geo-sharded clusters.

Supports Google Cloud Peering.
Introduces Analytics Nodes. These are similar to read-only nodes but this special node type makes use of replica set tags to let you target workloads to specific secondaries.
Support for AWS Stockholm region. With this region comes a new largest cluster, M700.
Atlas on Azure 2.0.
- M10, M80, and M200 clusters are now supported in all regions. The M90 tier is going to be removed shortly.
- Pricing reductions in most regions.
- All Azure clusters have been migrated to latest generation hardware.

Optimizes safe cluster upgrades after failure (no user-facing components, internal Atlas planner optimizations).
Allows creation of API Keys that are scoped to an organization and are not tied to a human.
Credit cards will be authorized for a small amount ($1.00) to reduce the risk of failed charges.
Users can now remove themselves from a project.

Optimizes automated rollout to ensure that rollouts happen within 1 U.S. East business day for non-maintenance-window projects.
Provides more visibility to maintenance timing in the administration user interface.
Supports On-Demand Cloud Provider Snapshots.

Improved experience for connecting to cluster.
Can now set advanced configuration options when deploying the Business Intelligence Connector.
Can restrict MongoDB employee access to their Atlas servers.
Can use Snapshot Backups for sharded clusters AWS and Azure as private beta.
Can now create rolling indexes via Data Explorer.

Ability for Project Owners to disable the use of Data Explorer for their Project.

← Release Notes Data Lake Changelog →