> This page location: /docs.md > /docs/management.md > /docs/atlas/create-connect-deployments.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Manage Global Clusters

**Important:**

The feature described on this page is not currently supported on Atlas Infinite clusters during public preview. For the features supported in public preview, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing/#public-preview-availability)

Use the following resources to configure and manage your Global Clusters. For general cluster configuration, see [Manage Clusters.](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-manage-clusters)

Atlas Global Clusters require that you define single or multi-region Zones, where each zone supports write and read operations from geographically local shards. You can also configure zones that support global low-latency secondary reads. To learn more about Global Cluster zones and how to configure them, see [Global Write Zones and Zone Mapping.](https://www.mongodb.com/docs/atlas/global-clusters.md#std-label-global-writes-zones)

## Global Write Zones and Zone Mapping

Each Atlas Global Cluster supports up to nine distinct zones. Each zone consists of one Highest Priority region and one or more Electable, Read-only, or Analytics regions. The available regions depend on the selected cloud service provider.

| Region Type | Description |
| --- | --- |
| Highest Priority | Region where Atlas deploys the [primary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) replica set member for the shard or shards associated with that zone. Clients can issue write operations only to the [primary.](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) Atlas uses the geographic location of the Highest Priority regions to construct a map of geographically-near countries and subdivisions. The Global Writes cluster uses this map for directing write operations to the correct zone. To facilitate low-latency local secondary reads of globally distributed data, for each zone in the cluster, add a Read-only node in the Highest Priority region of every other cluster zone. |
| Electable | Region where Atlas deploys the electable [secondary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-secondary) replica set members for the shard or shards associated to that zone. Electable regions add additional fault tolerance in the event of a partial or total regional outage in the Highest Priority region. |
| Read-only | Region where Atlas deploys the non-electable [secondary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-secondary) replica set members for supporting secondary read operations. |
| Analytics | Region where Atlas deploys [analytics nodes](https://www.mongodb.com/docs/atlas/reference/faq/deployment.md#std-label-analytics-nodes-overview). Analytics nodes are read-only nodes configured with distinct [replica set tags](https://www.mongodb.com/docs/atlas/reference/replica-set-tags.md#std-label-replica-set-tags). You can use these tags to direct queries to specific regions. As a result, analytics nodes can help isolate reporting queries from your normal operational workload as well as reduce latency for local reads. |

### Shard Distribution

For each shard associated to a zone, Atlas distributes the shard nodes across the configured regions. If your cluster is located in a large geographic continent, create multiple zones to direct global writes to shards that are closer to your users.

**Note:**

Atlas supports up to [70 shards per sharded cluster](https://www.mongodb.com/docs/atlas/reference/faq/deployment.md#std-label-can-i-deploy-more-than-50-shards) regardless of the number of zones. If you have requirements for more shards in your Global Cluster, [contact support.](https://www.mongodb.com/docs/atlas/support.md#std-label-atlas-support)

In Atlas, go to the Support page.

If it's not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

Click the Support icon in the navigation bar.

Click View plan.

The [Support](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Fsupport) page displays.

The Atlas cluster builder includes templates for automatically configuring Global Writes zones for the Global Cluster. Each template provides a visual description of the cluster zone configuration, including estimates of geographic latency and coverage.

### Configure Zone Mappings

Before you can configure zone mappings for a Global Cluster, you must [create a Global Cluster.](https://www.mongodb.com/docs/atlas/tutorial/create-global-cluster.md#std-label-create-new-global-write-cluster)

To configure your existing Global Cluster:

1. In Atlas, go to the Clusters page for your project.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the sidebar, click Clusters under the Database heading.

   The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

2. Configure your existing Global Cluster.

   Click Edit Config and select the cluster you want to modify from the drop-down menu.

   In the dialog box that appears, complete the steps to [configure your zones.](https://www.mongodb.com/docs/atlas/tutorial/create-global-cluster/#configure-your-zones)

**Note:**

Atlas doesn't automatically configure or shard collections. You can use the Atlas UI to [shard a global collection for global writes](https://www.mongodb.com/docs/atlas/shard-global-collection.md#std-label-de-shard-collection-for-global-writes) if your global cluster uses [Atlas-Managed Sharding](https://www.mongodb.com/docs/atlas/tutorial/create-global-cluster/#select-your-sharding-configuration) and the collection meets the [compatibility requirements.](https://www.mongodb.com/docs/atlas/shard-global-collection.md#std-label-global-writes-collections)

### Considerations

- If you are using the [standard connection string format](https://www.mongodb.com/docs/manual/reference/connection-string-formats.md#std-label-connections-standard-connection-string-format) rather than the DNS (Domain Name Service) seedlist format, removing an entire zone from an existing global cluster may result in a new connection string.

  To verify the correct connection string after deploying the changes:

  1. In Atlas, go to the Clusters page for your project.

     If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

     If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

     In the sidebar, click Clusters under the Database heading.

     The [Clusters](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fclusters) page displays.

  2. Verify the connection string.

     Click Connect.

- When Global Writes are enabled, Global Clusters do not support dedicated search nodes.

- Flex clusters don't support Global Clusters at this time. To learn more, see [Atlas Flex Limitations.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-cluster-limitations)
