> This page location: /docs.md > /docs/management.md > /docs/atlas/create-connect-deployments.md > /docs/atlas/manage-clusters.md > /docs/atlas/customize-storage.md

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

<!--
Tab options on this page. Append to the .md URL to filter:
  ?tabs=<id,...>   select specific tabs (e.g. ?tabs=nodejs,shell)
  ?allTabs=true    include every tab
  (no param)       default: one tab per tabset

Available tabs:
  other tabs: americas, europe, asia-pacific
-->

# NVMe Storage for Atlas Clusters

For applications hosted on [AWS](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-amazon-aws) or  [Azure](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure) that require low-latency and high-throughput I/O, Atlas offers storage options using locally attached ephemeral NVMe (non-volatile memory express) SSD (Solid State Disk)s.

**Note:**

Atlas doesn't support NVMe (non-volatile memory express) clusters on Google Cloud. NVMe (non-volatile memory express) clusters are not compatible with independent shard scaling.

## Tier Support

The following cluster tiers support NVMe (non-volatile memory express) clusters on AWS (Amazon Web Services):

- `M40`

- `M50`

- `M60`

- `M80`

- `M200`

- `M400`

On AWS (Amazon Web Services), NVMe (non-volatile memory express) storage is supported on Gen2 Dedicated clusters.

The following cluster tiers support NVMe (non-volatile memory express) clusters on Azure (Microsoft Azure):

- `M60`

- `M80`

- `M200`

- `M300`

- `M400`

- `M600`

The fixed-value storage space and RAM for an NVMe (non-volatile memory express) cluster corresponds to its cluster tier. To learn more, see [Amazon Cluster Configuration Options](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-amazon-aws-configuration-options) and [Azure Cluster Configuration Options.](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-configuration-options)

## Region Support

To see which AWS (Amazon Web Services) regions support NVMe (non-volatile memory express) storage, see [AWS Gen2 Region Support.](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-aws-reference-gen2-regions)

Atlas supports NVMe (non-volatile memory express) clusters in the following Azure (Microsoft Azure) regions:

### Americas

| Azure Region | Location | Atlas Region |
| --- | --- | --- |
| `brazilsouth` | São Paulo, Brazil | `BRAZIL_SOUTH` |
| `canadacentral` | Toronto, ON | `CANADA_CENTRAL` |
| `centralus` | Iowa, USA | `US_CENTRAL` |
| `eastus` | Virginia (East US) | `US_EAST` |
| `eastus2` | Virginia, USA | `US_EAST_2` |
| `southcentralus` | Texas, USA | `US_SOUTH_CENTRAL` |
| `westus3` | El Mirage, Arizona | `US_WEST_3` |

### Availability Zones

NVMe (non-volatile memory express) clusters in the following Azure (Microsoft Azure) regions have two [Availability Zones:](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-availability-zones)

- `eastus2`

- `centralus`

- `southcentralus`

NVMe (non-volatile memory express) clusters in all other Azure (Microsoft Azure) regions that [indicate Availability Zones](https://www.mongodb.com/docs/atlas/reference/microsoft-azure.md#std-label-microsoft-azure-supported-regions) have three Availability Zones.

## Considerations

NVMe (non-volatile memory express) instances can't be used in multi-cloud clusters.

Atlas Infinite doesn't support locally attached NVMe (non-volatile memory express) SSD (Solid State Disk) storage in public preview. For the features supported in public preview, see [Public Preview Availability.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-availability)

Clusters with NVMe (non-volatile memory express) storage use [Cloud Backups](https://www.mongodb.com/docs/atlas/backup/cloud-backup/overview.md#std-label-backup-cloud-provider). You can't disable backup on NVMe (non-volatile memory express) clusters. If you want to use hourly backups, Atlas limits backups on NVMe (non-volatile memory express) clusters to once every 12 hours.

NVMe (non-volatile memory express) clusters use a [hidden secondary node](https://www.mongodb.com/docs/manual/core/replica-set-hidden-member.md#std-label-replica-set-hidden-members) that consists of a provisioned volume with high throughput and IOPS (Input/Output Operations per Second) to facilitate backup.

You can't [pause](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-pause-cluster) an NVMe (non-volatile memory express) cluster.

On Atlas Core clusters, scaling of clusters (including [auto-scaling](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling)) that use the local NVMe (non-volatile memory express) SSD storage option requires an [initial sync](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-initial-sync), and always uses [a File Copy Based Initial Sync](https://www.mongodb.com/docs/manual/core/replica-set-sync/#file-copy-based-initial-sync) to sync all the nodes of an NVME cluster whenever an initial sync is required. Atlas NVMe (non-volatile memory express) clusters auto-scale to the next higher tier when 90% of the storage space is full. An [initial sync](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-initial-sync) takes longer to complete compared to subsequent syncs, and reduces the performance of the [primary](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-primary) from which the data is read.
