> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Amazon Web Services (AWS) Atlas Infinite is available as a Public Preview feature. Atlas Infinite and its documentation might change at any time during the Preview period. To learn more, see [Preview Features](https://www.mongodb.com/docs/preview-features/). Atlas supports deploying clusters onto Amazon Web Services (AWS). Atlas supports all AWS (Amazon Web Services) regions other than some regions in China and US GovCloud. While Atlas does not support US GovCloud regions, MongoDB Atlas for Government does. To learn about supported government regions, see [Supported Cloud Providers and Regions.](https://www.mongodb.com/docs/atlas/government/overview/supported-regions/) Atlas supports the following AWS (Amazon Web Services) regions. While all of the following regions support dedicated clusters (`M10+`), some regions don't support free and Atlas Flex clusters. The Atlas [API](https://www.mongodb.com/docs/atlas/api.md#std-label-graphql-api-overview) uses the corresponding Atlas Region. The **Atlas Infinite Support** column shows the regions for clusters on [Atlas Infinite Edition](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-landing.md#std-label-atlas-infinite-edition) in public preview. ### Americas | AWS Region | Location | Atlas Region | Free cluster/Atlas Flex Support | `M10+` Support | Atlas Infinite Support | | --- | --- | --- | --- | --- | --- | | `us-east-1` | Northern Virginia, USA | `US_EAST_1` | | | | | `us-west-2` | Oregon, USA | `US_WEST_2` | | | | | `ca-central-1` | Montreal, QC, Canada | `CA_CENTRAL_1` | | | | | `ca-west-1` | Calgary, Canada | `CA_WEST_1` | | | | | `us-east-2` | Ohio, USA | `US_EAST_2` | | | | | `us-west-1` | Northern California, USA | `US_WEST_1` | | | | | `sa-east-1` | Sao Paulo, Brazil | `SA_EAST_1` | | | | | `mx-central-1` | Querétaro, Mexico | `MX_CENTRAL_1` | | | | In the second half of 2025, the IP addresses of nodes deployed to `ap-southeast-7` and `mx-central-1` might change to accommodate future growth of Atlas in these geographies. This page provides reference material related to Atlas cluster deployments on AWS (Amazon Web Services). ## Cluster Configuration Options Each Atlas cluster tier comes with a default set of resources. Atlas provides the following resource configuration options: Custom Storage Size The size of the server root volume. Atlas clusters deployed onto AWS (Amazon Web Services) use general purpose SSD (Solid State Disk)s. **Note: RAM Availability** The actual amount of RAM available to each cluster tier might be slightly less than the stated amount, due to memory that the kernel reserves. The following cluster tiers are available: | Instance Size | Storage Range | Default Storage | Default RAM | | --- | --- | --- | --- | | M0 | .5 GB | .5 GB | Shared | | Flex | 5 GB | 5 GB | Flex | | M10 | 10 GB to 128 GB | 10 GB | 2 GB | | M20 | 10 GB to 255 GB | 20 GB | 4 GB | | M30 | 10 GB to 512 GB | 40 GB | 8 GB | | M40 | 10 GB to 1 TB | 80 GB | 16 GB | | M40 Low-CPU | 10 GB to 1 TB | 80 GB | 16 GB | | M40_NVME | 380 GB | 380 GB | 15.25 GB | | M50 | 10 GB to 4 TB | 160 GB | 32 GB | | M50 Low-CPU | 10 GB to 4 TB | 160 GB | 32 GB | | M50_NVME | 760 GB | 760 GB | 30.5 GB | | M60 | 10 GB to 4 TB | 320 GB | 64 GB | | M60 Low-CPU | 10 GB to 4 TB | 320 GB | 64 GB | | M60_NVME | 1.6 TB | 1.6 TB | 61 GB | | M80 | 10 GB to 4 TB | 750 GB | 131 GB | | M80 Low-CPU | 10 GB to 4 TB | 750 GB | 122 GB | | M80_NVME | 1.6 TB | 1.6 TB | 122 GB | | M140 | 10 GB to 4 TB | 1 TB | 192 GB | | M200 | 10 GB to 4 TB | 1.5 TB | 256 GB | | M200 Low-CPU | 10 GB to 4 TB | 1.5 TB | 256 GB | | M200_NVME | 3.1 TB | 3.1 TB | 244 GB | | M300 | 10 GB to 4 TB | 2 TB | 384 GB | | M300 Low-CPU | 10 GB to 4 TB | 2 TB | 384 GB | | M400 Low-CPU | 10 GB to 4 TB | 3 TB | 488 GB | | M400_NVME | 4 TB | 4 TB | 512 GB | | M700 Low-CPU | 10 GB to 4 TB | 4 TB | 768 GB | Can use this tier for a multi-cloud cluster. Unavailable in the **AP\_SOUTHEAST\_2** region. Unavailable in the **AP\_SOUTHEAST\_6** and **AP\_EAST\_2** regions. **Note: Cluster Tier & API Naming Conventions** For purposes of management with the [Atlas Administration API](https://www.mongodb.com/docs/atlas/api.md#std-label-atlas-api), cluster tier names that are prepended with `R` instead of an `M` (`R40` for example) run a [low-CPU](https://www.mongodb.com/docs/atlas/customize-storage.md#std-label-storage-class-ui) version of the cluster. When [creating](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster) or [modifying](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupcluster) a cluster with the API, be sure to specify your desired cluster class by name with the `replicationSpecs[n].regionConfigs[m].electableSpecs.instanceSize` attribute. **Important: Multi-Cloud Low-CPU clusters** Low-CPU cluster tiers (M40 Low-CPU, M50 Low-CPU, M60 Low-CPU, and so on) are available in [multi-cloud cluster configurations](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-create-cluster-multi-region) as long as the cluster tier is available for all the regions that the cluster uses. Workloads typically require less than `2TB`. Custom Storage Speed The input/output operations per second (IOPS) the system can perform. Each cluster has a default IOPS (Input/Output Operations per Second) rate. You can also choose to provision your tier's IOPS (Input/Output Operations per Second) rate to meet your particular needs. The selected cluster tier and custom storage size dictate the maximum IOPS (Input/Output Operations per Second) for each storage speed. Encrypted Storage Volumes Encrypts the root volume for data at rest inside the volume and all data moving between the volume and the cluster. Atlas uses [Amazon EBS encryption.](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html) ## Amazon Availability Zones Each AWS (Amazon Web Services) region includes a set number of independent availability zones. Availability Zones consist of one or more discrete data centers, each with redundant power, networking and connectivity, housed in separate facilities. For regions that have at least three availability zones (3AZ), Atlas deploys clusters across three availability zones. For regions that only have two availability zones (2AZ), Atlas deploys clusters across two availability zones. The Atlas [Add New Cluster](https://www.mongodb.com/docs/atlas/tutorial/create-new-cluster.md#std-label-create-new-cluster) form marks regions that support at least three availability zones as Recommended, as they provide higher availability. The number of availability zones in a region has no effect on the number of MongoDB nodes Atlas can deploy. MongoDB Atlas clusters are always made of replica sets with a minimum of three MongoDB nodes. For more information on the number of availability zones in a given region, see the Amazon documentation on [global infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/). For more information on AWS (Amazon Web Services) regions and availability zones, see the Amazon documentation on [using regions and availability zones.](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) ### Regions with at Least Three Availability Zones Atlas clusters deployed in regions with at least three availability zones are split across three availability zones. For example, a three node replica set cluster would have one node deployed onto each availability zone. ![A 3-node replica set deployed across a 3-availability zone AWS region.](/images/amazon-aws-3az.svg) 3AZ (Three Availability Zone) clusters have higher availability compared to 2AZ (Two Availability Zone) clusters. However, not all regions support 3AZ (Three Availability Zone) clusters. ### Regions with Only Two Availability Zones Atlas clusters deployed in regions with two availability zones are split across the two availability zones. For example, a three node replica set cluster would have two nodes deployed to one availability zone and the remaining node deployed to the other availability zone. ![A 3-node replica set deployed across a 2-availability zone AWS region.](/images/amazon-aws-2az.svg) 2AZ (Two Availability Zone) clusters have a higher chance of loss of availability in the event of the loss of an availability zone than 3AZ (Three Availability Zone) clusters. However, where latency or location are a priority, a region that supports 2AZ (Two Availability Zone) clusters may be preferred. ## Atlas Infinite Storage IOPs and Throughput Values per Cluster Tier On Atlas Infinite clusters, storage performance is fixed per cluster tier. The storage IOPS (Input/Output Operations per Second) and storage throughput available to a cluster don't change as the amount of data you store grows. To change storage performance, change the cluster tier. On Atlas Core clusters, storage performance scales with storage capacity instead. The Atlas UI shows the storage IOPS (Input/Output Operations per Second) and storage throughput for the selected tier on the Cluster Tier card. These values are read-only. The cluster tier determines both values. The following table shows the storage IOPS (Input/Output Operations per Second) and storage throughput for each Atlas Infinite cluster in public preview: | Cluster Tier | Storage IOPS | Storage Throughput | | --- | --- | --- | | `M10` | 625 | 10 MBps | | `M20` | 1,250 | 20 MBps | | `M30` | 5,000 | 80 MBps | | `M40` | 9,375 | 150 MBps | | `M40` Low-CPU | 5,000 | 80 MBps | | `M50` | 18,750 | 300 MBps | | `M50` Low-CPU | 9,375 | 150 MBps | | `M60` | 37,500 | 600 MBps | | `M60` Low-CPU | 18,750 | 300 MBps | The storage IOPS (Input/Output Operations per Second) values are reference values intended to illustrate a baseline. These values assume a 16 kB I/O size. The maximum IOPS (Input/Output Operations per Second) that a cluster achieves varies based on the characteristics of your workload. ## AWS Gen2 Dedicated clusters Atlas supports configuring `M30+` Dedicated clusters deployed on AWS (Amazon Web Services) as [Gen2 clusters.](https://www.mongodb.com/docs/atlas/manage-clusters.md#std-label-gen2-clusters) `M30+` Atlas Infinite clusters are available on Gen2 only, and don't support Extended Standard IOPS (Input/Output Operations per Second). To learn more about how Atlas Infinite clusters handle storage and IOPS (Input/Output Operations per Second), see [Manage Storage on an Atlas Infinite Cluster](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage) and [Atlas Infinite Storage IOPs and Throughput Values per Cluster Tier.](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-atlas-infinite-storage-iops-throughput-values) ### Available Cluster Tiers The following tables show the AWS (Amazon Web Services) instance, vCPU counts, and RAM for each supported Gen2 cluster tier: **Note:** The following instance families are the preferred and primary instance families for Gen2 cluster on AWS (Amazon Web Services). ### General | Atlas Gen2 Tier | M8g Instance | vCPU | RAM | | --- | --- | --- | --- | | M30 | `m8g.large` | 2 | 8 GiB | | M40 | `m8g.xlarge` | 4 | 16 GiB | | M50 | `m8g.2xlarge` | 8 | 32 GiB | | M60 | `m8g.4xlarge` | 16 | 64 GiB | | M80 | `m8g.8xlarge` | 32 | 128 GiB | | M140 | `m8g.12xlarge` | 48 | 192 GiB | | M200 | `m8g.16xlarge` | 64 | 256 GiB | | M300 | `m8g.24xlarge` | 96 | 384 GiB | For information on the maximum sustained IOPS (Input/Output Operations per Second) rate for each instance type, see [Amazon's EBS-optimized instance type documentation.](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html) In some cases, the maximum IOPS (Input/Output Operations per Second) rate listed for a given instance type in the Amazon AWS Documentation may be higher than the IOPS (Input/Output Operations per Second) rate Atlas allows you to configure. This is to ensure high availability, as some higher IOPS (Input/Output Operations per Second) rates can only be sustained for short periods of time. ### Supported Regions The following tables list the AWS (Amazon Web Services) regions that support Gen2 Dedicated clusters. The Atlas [API](https://www.mongodb.com/docs/atlas/api.md#std-label-graphql-api-overview) uses the corresponding Atlas Region. ### Americas | AWS Region | Location | Atlas Region | General | Low-CPU | NVMe | | --- | --- | --- | --- | --- | --- | | `ca-central-1` | Montreal, QC, Canada | `CA_CENTRAL_1` | | | | | `mx-central-1` | Querétaro, Mexico | `MX_CENTRAL_1` | | | | | `sa-east-1` | Sao Paulo, Brazil | `SA_EAST_1` | | | | | `us-east-1` | Northern Virginia, USA | `US_EAST_1` | | | | | `us-east-2` | Ohio, USA | `US_EAST_2` | | | | | `us-west-1` | Northern California, USA | `US_WEST_1` | | | | | `us-west-2` | Oregon, USA | `US_WEST_2` | | | | ## Dedicated Search Nodes ### Supported Regions Atlas supports deploying separate [Search Nodes](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-configure-search-nodes) for `M10` and higher clusters in the following AWS (Amazon Web Services) regions: ### Americas | AWS Region | Location | Atlas Region | | --- | --- | --- | | `us-east-1` | Northern Virginia, USA | `US_EAST_1` | | `us-west-2` | Oregon, USA | `US_WEST_2` | | `ca-central-1` | Montreal, QC, Canada | `CA_CENTRAL_1` | | `us-east-2` | Ohio, USA | `US_EAST_2` | | `us-west-1` | Northern California, USA | `US_WEST_1` | | `sa-east-1` | Sao Paulo, Brazil | `SA_EAST_1` | | `mx-central-1` | Querétaro, Mexico | `MX_CENTRAL_1` | **Note:** In the following AWS (Amazon Web Services) regions, Atlas supports only low-CPU search tiers: - Querétaro, Mexico (`mx-central-1`) - Thailand (`ap-southeast-7`) - Hyderabad, India (`ap-south-2`) - Hong Kong, China (`ap-east-1`) - Milan, Italy (`eu-south-1`) - Tel Aviv, Israel (`il-central-1`) - UAE (`me-central-1`) ### Available Search Tiers Atlas provides various [search tiers](https://www.mongodb.com/docs/atlas/cluster-config/multi-cloud-distribution.md#std-label-select-tiers-for-search-nodes) for Search Nodes deployed on AWS (Amazon Web Services). The following table lists the search tiers available for each class of hardware (low-CPU, high-CPU, storage-optimized), with default RAM and storage measured in gibibytes (GiB): ### Americas #### Low-CPU | Instance Size | Default RAM | Default Storage | vCPU | | --- | --- | --- | --- | | S30 | 8 GiB | 49 GiB | 1 | | S40 | 16 GiB | 98 GiB | 2 | | S50 | 32 GiB | 198 GiB | 4 | | S60 | 64 GiB | 396 GiB | 8 | | S80 | 128 GiB | 796 GiB | 16 | | S90 | 256 GiB | 1592 GiB | 32 | | S100 | 384 GiB | 2387 GiB | 48 | | S110 | 512 GiB | 3185 GiB | 64 | #### High-CPU | Instance Size | Default RAM | Default Storage | vCPU | | --- | --- | --- | --- | | S10 | 4 GiB | 54 GiB | 1 | | S20 | 4 GiB | 98 GiB | 2 | | S30 | 8 GiB | 198 GiB | 4 | | S40 | 16 GiB | 396 GiB | 8 | | S50 | 32 GiB | 796 GiB | 16 | | S60 | 64 GiB | 1592 GiB | 32 | | S70 | 96 GiB | 2387 GiB | 48 | | S80 | 128 GiB | 3185 GiB | 64 | #### Storage-Optimized | Instance Size | Default RAM | Default Storage | vCPU | | --- | --- | --- | --- | | S40 | 16 GiB | 392 GiB | 2 | | S50 | 32 GiB | 785 GiB | 4 | | S60 | 64 GiB | 1571 GiB | 8 | | S80 | 128 GiB | 3143 GiB | 16 | | S90 | 256 GiB | 6286 GiB | 32 | ## Stream Processing Workspaces **Important:** To request an unlisted region, add your feedback to the [MongoDB Feedback Portal](https://feedback.mongodb.com/?category=7529546585152608284). Your input helps prioritize future expansions of Atlas Stream Processing coverage. Atlas supports deploying [Stream Processing Workspaces](https://www.mongodb.com/docs/atlas/atlas-stream-processing/manage-processing-instance.md#std-label-atlas-sp-manage-spi) in the follow AWS (Amazon Web Services) regions: ### Americas | AWS Region | Location | Atlas Region | | --- | --- | --- | | `us-east-1` | Northern Virginia, USA | `US_EAST_1` | | `us-east-2` | Ohio, USA | `US_EAST_2` | | `us-west-2` | Oregon, USA | `US_WEST_2` | | `ca-central-1` | Montreal, QC, Canada | `CA_CENTRAL_1` | | `sa-east-1` | Sao Paulo, Brazil | `SA_EAST_1` | ## Integrations Along with [global region support](https://www.mongodb.com/docs/atlas/reference/amazon-aws.md#std-label-amazon-aws), the following product integrations enable applications running on AWS (Amazon Web Services), such as Amazon EC2, AWS Lambda, and Amazon Elastic Container Service (ECS), to use Atlas instances easily and securely. ### Networking Services - AWS PrivateLink: [Set up private endpoints with AWS](https://www.mongodb.com/docs/atlas/security-configure-private-endpoints.md#std-label-private-endpoint) - AWS Virtual Private Cloud (VPC): [Set up network peering connections with AWS](https://www.mongodb.com/docs/atlas/security-vpc-peering.md#std-label-vpc-peering) ### Security and Identity Services - AWS Identity Access Management (IAM) [Configure database users with IAM authentication](https://www.mongodb.com/docs/atlas/security-add-mongodb-users.md#std-label-mongodb-users) - AWS Key Management Service (KMS): - [Configure Atlas disk encryption with KMS](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption) - [Configure client-side field level encryption with KMS](https://www.mongodb.com/docs/manual/core/csfle/) - AWS SSO: [Configure federated authentication to the MongoDB UI](https://aws.amazon.com/blogs/apn/how-to-integrate-aws-single-sign-on-with-mongodb-atlas/) ### Other AWS Services - AWS CloudFormation: [Deploy and manage Atlas from CloudFormation](https://www.mongodb.com/blog/post/deploy-manage-mongodb-atlas-aws-cloud-formation) - Amazon EventBridge: [Atlas Triggers integration with Amazon EventBridge](https://www.mongodb.com/docs/atlas/atlas-ui/triggers/aws-eventbridge.md#std-label-atlas-aws-eventbridge) - Amazon Kinesis: [Send data to Atlas via Kinesis Data Firehose](https://aws.amazon.com/blogs/big-data/integrating-the-mongodb-cloud-with-amazon-kinesis-data-firehose/) - AWS S3: [Configure Atlas Data Federation to query data from S3](https://www.mongodb.com/docs/atlas/data-federation/config/adf-config-file-formats.md#std-label-adf-configuration-file-aws) ### Procurement - AWS Marketplace: [Pay for Atlas usage via AWS](https://aws.amazon.com/marketplace/seller-profile?id=c9032c7b-70dd-459f-834f-c1e23cf3d092) ## More Information For more information on how to use AWS (Amazon Web Services) with Atlas most effectively, review the following best practices, guides, and case studies: - AWS App Runner: [Build Applications and APIs Faster with MongoDB Atlas and AWS App Runner](https://www.mongodb.com/blog/post/build-applications-and-apis-faster-with-mongodb-atlas-and-aws-app-runner) - AWS Lambda: [Best Practices Connecting from AWS Lambda](https://www.mongodb.com/docs/atlas/manage-connections-aws-lambda.md#std-label-atlas-lambda-connections)