Navigation

Atlas Changelog

  • Changes the cluster-level navigation UI so that Atlas Search is now a top level tab.
  • Introduces a visual editor for creating an Atlas Search index.
  • Allows users of the BI Connector for Atlas to download BI Connector logs.
  • Introduces custom archiving rules for Atlas Online Archive.
  • Introduces an optional connection string for Atlas Online Archive that enables querying of archived data only (instead of the union of cluster and archive data).

  • Enables Multi-Cloud Clusters to be used with the following:

  • Introduces improvements to the Billing Invoice Summary table including a summary of usage by top line product categories.
  • Introduces Voice and SMS Factors as options for use with Okta multi-factor authentication.
  • Offers self-serve customers the option to sign up for Atlas Pro support.
  • Introduces Low-CPU clusters into additional Google Cloud regions: us-east1 (South Carolina), us-east4 (Virginia), and australia-southeast1 (Sydney).
  • Introduces availability zones for new clusters in the Azure Canada Central region.

  • Introduces a new project setting for advanced multi-region private endpoint use.

    • The project setting requires that all clusters in a project be sharded clusters. When enabled, customers are able to configure multiple private endpoints in multiple regions and connect via regionalized connection strings.
    • When this setting is disabled (the default), only a single private endpoint can be created per region for a multi-region project. (For a single region project, multiple private endpoints have always been supported.)
  • Updates terminology for API Access List management. Introduces API Access List for Programmatic API Keys and deprecates API whitelist.

  • Supports the following AWS regions:

    • af-south-1 (Cape Town, South Africa)
    • eu-south-1 (Milan, Italy)

  • Supports the following GCP regions:

    • asia-southeast2 (Jakarta, Indonesia)
    • uswest3 (Las Vegas, NV, USA)
    • uswest4 (Salt Lake City, UT, USA)

  • Supports the following Azure regions:

    • westcentralus (Wyoming, USA)
    • germanynorth (Berlin, Germany)
  • Updates terminology for Atlas cluster firewall management. Introduces IP Access List and deprecates "IP Whitelist".
  • Introduces new host-level monitoring metrics for total memory, total memory free and total swap used.

  • Reduces cluster pricing and introduces new storage options for Atlas on Azure:

    • M10 clusters include 8 GB of storage
    • M20 clusters include 16 GB of storage
    • M40 clusters include 64 GB of storage
  • Allows you to scope database users to one or more specific clusters and Data Lakes in an Atlas project.

Introduces easier authorization management for S3 access:

  • Provides a centralized UI to authorize and view AWS IAM roles and associated Data Lakes under the Atlas Project Integrations.
  • Allows you to re-use an existing AWS IAM role when granting access to a new Atlas Data Lake.
  • Introduces general availability of MongoDB 4.4.
  • Introduces Cross-Org Billing for customers on annual subscriptions.
  • Changes default for new Atlas cluster deployments to TLS 1.2 from TLS 1.1.
  • Adds Atlas Search support for geospatial search queries and autocomplete features.
  • Redesigns the MongoDB Cloud navigation.
  • Introduces schema suggestions in Performance Advisor and Data Explorer.
  • Reduces the price of NVMe storage for AWS clusters.

  • Supports the following advanced federation options for customers who use SAML -based single sign-on:

    • Restrict organization membership
    • Restrict access by domain
    • Bypass single sign-on
  • Removes legacy Legacy Backup as an option for new GCP - and Azure -backed clusters. New GCP - and Azure -backed clusters use Cloud Backups for backup.

  • Supports multiple connection strings to the same cluster:

    • Supports deploying a multi-region Atlas cluster on Azure and connecting to it using VNet peering.
    • Supports using MongoDB Realm to connect to an Atlas cluster that uses VPC peering on GCP or VNet peering on Azure.
    • Supports using MongoDB Charts to connect to an Atlas cluster that uses VPC peering on GCP or VNet peering on Azure.
    • Supports using Live Migration to migrate to an Atlas cluster where VPC peering on GCP or VNet peering on Azure is enabled.
    • Supports connecting from public IP using a special connection string to an Atlas cluster on GCP or Azure that is using peering.
    • Supports connecting to an Atlas cluster over an AWS VPC peering connection where you use a custom DNS provider (and AWS 's built in split horizon DNS cannot be used) and a special connection string for private IP.
  • Supports M0 Free Tier and M2/M5 shared starter clusters in the GCP Mumbai region.
  • M10 and M20 cluster tiers now support Atlas Search. All cluster tiers running MongoDB version 4.2 and higher can use Atlas Search.
  • Supports the GCP Seoul region.

  • Supports the following Azure regions:

    • Azure Norway East
    • Azure Switzerland West: This non-standard Azure region should be used as a secondary disaster recovery region for Switzerland North.
    • Azure UAE Central: This non-standard Azure region should be used secondary disaster recovery region for UAE North.
  • Supports Continuous Cloud Backups for GCP and Azure backups.
  • Defaults new clusters to MongoDB 4.2.
  • Displays a review change modal to users after making edits to a cluster.
  • Supports "Click-to-Create" Index Suggestions in Performance Advisor.
  • Supports MongoDB 4.2 on AWS using Cloud Backups with Continuous Cloud Backup restores.
  • Transitions customers with Legacy Backups automatically to Cloud Backups when upgrading from 4.0 to 4.2.

  • Increases maximum storage to memory ratio:

    Cluster TiersOld Max Storage RatioNew Max Storage Ratio
    M10 - M4050:160:1
    M50+ cluster tiers100:1120:1

  • Increases number of connections to M10 and M20 tiers.

    Cluster TiersOld ConnectionsNew Connections
    M107501,500
    M201,5003,000
  • Starts port numbers from 1024 instead of 1 on Atlas Private Endpoints on AWS cluster nodes.

Starting week of 24 February:

  • Scales cluster to next cluster tier (from M30 to M40 for example) to continue storage scaling when the cluster:

    • Has enabled storage auto-scaling, and
    • Approaches the cluster tier’s maximum storage level
  • Supports using Google authentication for MongoDB Cloud user login.
  • Introduces account.mongodb.com: a unified login experience for MongoDB Cloud, Support, JIRA, and Feedback.
  • Removes Legacy Backup as a backup option for new AWS -backed clusters. Newly deployed AWS -backed clusters use Cloud Backups for backup.
  • Provides customers with project-level maintenance windows enabled with ability to receive the 72-hour alert notification in their configured alerts destination.
  • Modifies behavior so that clusters enter a terminal state after customers revoke MongoDB Atlas encryption keys that they manage with AWS KMS , GCP KMS , or Azure Key Vault.
  • Provides ability to manage AWS PrivateLink via API.
  • Supports M0 Free Tier and M2/M5 shared starter clusters in the GCP Japan (Tokyo) and Azure Canada Central (Toronto) regions.
  • Introduces Atlas Triggers integration with Amazon EventBridge.
  • Introduces Identity Federation with SAML.

  • Supports higher maximum connection limits for new cluster deployments on select cluster tiers:

    • M10 lifted from 350 to 1,500
    • M20 lifted from 700 to 3,000
    • M30 lifted from 2,000 to 3,000
    • M40 lifted from 4,000 to 6,000

  • 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 Backup backups.
  • 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 MongoDB Realm/Charts-created database users and IP access list entries no longer show in the Atlas console.
  • 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.
  • 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.
  • Support for GCP Osaka region.
  • Support to search for organization or project names that are one character long.
  • Cloud Backups 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 Legacy Backup or the Cloud Backups 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 Backups 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 Backups.
  • Allow users to set when they would prefer to start Atlas maintenance.
  • Support NVMe storage.
  • Create and manage custom roles for database users.
  • Can peer across regions.
  • Improved speed of backup restores for Legacy Backup.
  • Improved the Cluster Connect experience.
  • Support for sharded clusters for Snapshot Backup in both AWS and Azure.

  • Support for new GCP regions:

    • Finland
    • Los Angeles
    • Hong Kong
  • 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.
  • Encrypted Storage Engine available with Azure KeyVault integration
  • Data Explorer Available for Atlas Shared Tier (M0/M2/M5)
  • Public API: Ability to perform point in time automated restores
  • Send project alert notifications to organization members by role

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.

Give Feedback