Manage Project Settings

Update Project Settings

To update settings for the project you specify using the Atlas CLI, run the following command:

atlas projects settings update [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas projects settings update.

View Project Settings

To return the settings details for the project you specify using the Atlas CLI, run the following command:

atlas projects settings describe [options]

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas projects settings describe.

Configure Custom DNS on AWS

Use the following commands to configure custom DNS settings on AWS.

atlas customDns aws enable [options]

atlas customDns aws disable [options]

atlas customDns aws describe [options]

Project Name

The Project Name setting sets your project's name.

You must have the Project Owner role for the project or the Organization Owner role for the project's organization to edit the project name.

Project Time Zone

The Project Time Zone setting sets your project's time zone. This affects the maintenance window timezone and alerts, but not the timezone set for individual user accounts. [1]

There is also a User Preferences timezone, which only affects the activity feed.

Tags

The Tags setting allows you to label and organize your projects with key-value pairs. To learn more, see Tags on Projects.

Connect via Peering Only (GCP and Azure)

The Connect via Peering Only (GCP and Azure) setting allows you to enable or disable connections between MongoDB Atlas dedicated clusters and public IP addresses outside of the peered VPC/VNet. You can only enable or disable this setting when there are no active dedicated GCP or Azure clusters in your project.

IMPORTANT: This feature has been deprecated. Existing clusters can continue to use this feature. Use both Standard and Private IP for Peering connection strings to connect to your project. These connection strings allow you to connect using both VPC/VNet Peering and allowed public IP addresses. To learn more about support for multiple connection strings, see this FAQ.

Using Custom DNS on AWS with VPC Peering

The Using Custom DNS on AWS with VPC Peering setting allows you to expose a second connection string for your dedicated Atlas clusters on AWS that resolves to private IPs.

Enable this setting if you use custom DNS that cannot take advantage of AWS built-in split-horizon DNS across a VPC peering connection.

Atlas displays this setting only when you enable network peering on AWS.

Multiple Regionalized Private Endpoints

The Multiple Regionalized Private Endpoints setting allows you to create more than one Private Endpoint in more than one region for multi-region and global sharded clusters.

Enable this setting if you want to connect to multi-region or global sharded clusters using private endpoints.

WARNING: Your connection strings to existing multi-region and global sharded clusters change when you enable this setting.

You must update your applications to use the new connection strings. This might cause downtime.

You can enable this setting if your Atlas project contains only sharded clusters.

You can't disable this setting if you have:

• More than one private endpoint in more than one region, or

• More than one private endpoint in one region and one private endpoint in one or more regions.

You can only create sharded clusters when you enable the regionalized private endpoint setting. You can't create replica sets.

Collect Database Specific Statistics

The Collect Database Specific Statistics setting allows you to enable or disable the collection of database statistics in cluster metrics.

Data Validation

The Data Validation setting controls automatic data validation for all clusters in the project.

Atlas validates data consistency across all clusters in a project by comparing data across replica set nodes. For clusters with encryption at rest using customer-managed keys, validation requires decrypting data with your key and stores inconsistency details for up to 90 days and run metadata for up to 3 years.

To learn more, see Data Validation for Cluster Consistency.

Set Preferred Cluster Maintenance Start Time

The Set Preferred Cluster Maintenance Start Time setting allows you to set which hour of the day Atlas starts weekly maintenance on your cluster.

To learn more about cluster maintenance windows, see Manage Cluster Maintenance.

Project Overview

The Project Overview setting sets the project landing page to Overview.

Overview is a home page for Atlas that displays modules for common Atlas actions.

Atlas enables the Overview page by default. To enable or disable the Overview page, you must have the Project Owner role.

Real Time Performance Panel

The Real Time Performance Panel setting allows you to see real-time metrics from your MongoDB database.

Data Explorer

The Data Explorer setting allows you to query your database with a graphical interface.

IMPORTANT: When Data Explorer is disabled, you cannot:

• Terminate slow operations from the Real-Time Performance Panel.

• Create indexes from the Performance Advisor. You can still view Performance Advisor recommendations, but you must create those indexes from mongosh.

• Use the Search Tester to run Search queries. You can still run Search queries using mongosh, Compass, or MongoDB drivers.

Performance Advisor and Profiler

The Performance Advisor and Profiler setting allows you to analyze database logs and receive performance improvement recommendations.

Schema Advisor

The Schema Advisor setting allows you to receive customized recommendations to optimize your data model and enhance performance.

Disable this setting to disable schema suggestions in the Performance Advisor and the Atlas UI.

Managed Slow Operations

The Managed Slow Operations setting dynamically sets the Slow Query Threshold based on execution times of operations across your cluster.

Disable this feature to set a fixed, user-specified slow query threshold.

Enable Extended Storage Sizes

The Enable Extended Storage Sizes setting allows you to configure clusters with greater maximum storage than the standard limit. Only clusters which meet the following criteria support extended storage:

• The cluster is on Azure, AWS, or Google Cloud

• If the cluster is on Azure, it is configured with enhanced type disks and in one of the following regions that support extended storage

• The cluster is an Atlas Core cluster.

• The cluster is either General or Low-CPU class

• The cluster is single-region. Extended Storage is not available for multi-region clusters.

• Extended storage is available for M40 tier and higher clusters with the following limitations:

  • M40: up to 4TB

  • M50/M60: up to 8TB

  • M80+: up to 14TB

  To change your cluster's tier, see Modify an Atlas Core Cluster.

If you enable extended storage, this slows down initial syncs and cross-project snapshot restores, and can reduce high availability. Enabling extended storage is a temporary solution for clusters that might require additional storage capacity in the future. We recommend that you enable sharding for long-term expanded storage capacity.

Native Reranking: $rerank Aggregation Stage

The Native Reranking: $rerank Aggregation Stage setting can enable or disable the $rerank aggregation stage. To learn more, see Enable or Disable Native Reranking.

If you enable Native Reranking, you can use the $rerank stage in your aggregation pipelines to reorder input documents by using Voyage AI's reranking models. This stage returns those documents sorted by relevance to the query. To learn more about $rerank, see $rerank.

Atlas uses Voyage AI reranking models, which incur usage-based costs. The model inference platform runs on MongoDB infrastructure in a Google Cloud cloud deployment in a US region. To learn more about billing for Native Reranking, see Manage Billing for Native Reranking.

The $rerank stage is available only on clusters running MongoDB 8.3 or later, and it is disabled by default.

Query Shape Reports

The Query Shape Reports setting controls whether Atlas sends Query Shape Report emails to Project Owner users in your project. The report summarizes inefficient query shapes for the clusters that you select in your project.

Atlas automatically subscribes the first cluster in a project that receives a Query Targeting: Scanned Objects / Returned alert. To learn more, see Query Shape Reports.

Only users with the Project Owner role can change this setting. The setting applies to the entire project. You cannot subscribe or unsubscribe individual users, but you can change which clusters the report covers.

Delete Charts

IMPORTANT: Deleting a MongoDB Charts instance deletes all data associated with that instance including dashboards, data sources, and metadata. Once the MongoDB Charts instance is deleted, this data cannot be recovered.

The Delete Charts setting allows Project Owners to delete the MongoDB Charts instance associated with your project. This setting is only visible if you have created a Charts instance for your project.

If you delete your linked MongoDB Charts instance, you can create a new MongoDB Charts instance for your project at any time. The newly created instance does not retain any data from previously deleted instances.

Delete Project

The Delete Project setting allows you to delete a project by clicking the Delete Project button.

Atlas guides you through a wizard that lists the project's resources and deletes them for you. You don't need to terminate clusters, applications, or other resources first. For more information, see Delete a Project.