MongoDB Atlas Release Notes¶

On this page

2019 Releases¶

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. You must delete all existing snapshots before switching between backup methods for an Atlas project.
Enhanced left-hand navigation.

Atlas instances 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 instance sizes 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 instance size, M700.
Atlas on Azure 2.0.
- M10, M80, and M200 instances are now supported in all regions. The M90 instance size is going to be removed shortly.
- Pricing reductions in most regions.
- All Azure instances 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.