Navigation

Amazon Web Services (AWS)

Atlas supports deploying clusters onto Amazon Web Services (AWS). Atlas supports all AWS regions other than those in China and US GovCloud.

The following table shows the supported AWS regions. The Atlas Region is the corresponding region name used by the Atlas API.

AWS RegionLocationAtlas RegionM0 Free Tier SupportM2/M5 Shared Tier Support
us-east-1Northern Virginia, USAUS_EAST_1
us-west-2Oregon, USAUS_WEST_2
ca-central-1Montreal, QC, CanadaCA_CENTRAL_1
us-east-2Ohio, USAUS_EAST_2
us-west-1Northern California, USAUS_WEST_1
sa-east-1Sao Paulo, BrazilSA_EAST_1

This page provides reference material related to Atlas cluster deployments on AWS .

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 use general purpose SSDs [1].
Info With Circle IconCreated with Sketch.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 SizeDefault StorageDefault RAM
M22 GBShared
M55 GBShared
M1010 GB2 GB
M2020 GB4 GB
M3040 GB8 GB
M4080 GB16 GB
M40 Low-CPU (R40)80 GB16 GB
M40_NVME380 GB15.25 GB
M50160 GB32 GB
M50 Low-CPU (R50)160 GB32 GB
M50_NVME760 GB30.5 GB
M60320 GB64 GB
M60 Low-CPU (R60)320 GB64 GB
M60_NVME1.6 TB61 GB
M80760 GB131 GB
M80 Low-CPU (R80)750 GB122 GB
M80_NVME1.6 TB122 GB
M1001 TB160 GB
M140 11 TB192 GB
M2001.5 TB256 GB
M200 Low-CPU (R200)1.5 TB256 GB
M200_NVME3.1 TB244 GB
M300 12 TB384 GB
M300 Low-CPU (R300)2 TB384 GB
M400 Low-CPU (R400)3 TB488 GB
M400_NVME 24 TB512 GB
M700 Low-CPU (R700)4 TB768 GB
1 Unavailable in the AP_SOUTHEAST_2 region.2 Availability limited to the following regions:
  • US_EAST_1
  • US_EAST_2
  • US_WEST_2
  • EU_WEST_1
  • EU_CENTRAL_1
  • AP_NORTHEAST_1
Info With Circle IconCreated with Sketch.Note
Cluster Tier & API Naming Conventions
For purposes of management with the Atlas API, cluster tier names that are prepended with R instead of an M (R40 for example) run a low-CPU version of the cluster. When creating or modifying a cluster with the API, be sure to specify your desired cluster class by name with the providerSettings.instanceSizeName attribute.
Important With Circle IconCreated with Sketch.Important
Multi-Cloud Low-CPU clusters
Low-CPU cluster tiers (R40, R50, R60, etc) are available in multi-cloud cluster configurations 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 rate. You can also choose to provision your tier's IOPS rate to meet your particular needs.The selected cluster tier and custom storage size dictate the maximum IOPS 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.

Each AWS 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 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.

For more information on AWS regions and availability zones, see the Amazon documentation on using regions and 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.

3AZ clusters have higher availability compared to 2AZ clusters. However, not all regions support 3AZ clusters.

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.

2AZ clusters have a higher chance of loss of availability in the event of the loss of an availability zone than 3AZ clusters. However, where latency or location are a priority, a region that supports 2AZ clusters may be preferred.

[1] For detailed documentation on Amazon storage options, see Amazon EBS Volume Types
Give Feedback