Amazon Web Services (AWS)¶
Synopsis¶
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 Region | Location | Atlas Region | M0 Free Tier Support | M2/M5 Shared Tier 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 | ||
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 |
This page provides reference material related to Atlas cluster deployments on AWS .
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 use general purpose SSDs [1].The following cluster tiers are available:NoteRAM AvailabilityThe actual amount of RAM available to each cluster tier might be slightly less than the stated amount, due to memory that the kernel reserves.
1 Unavailable in the AP_SOUTHEAST_2 region.2 Availability limited to the following regions:Instance Size Default Storage Default RAM M2 2 GB Shared M5 5 GB Shared M10 10 GB 2 GB M20 20 GB 4 GB M30 40 GB 8 GB M40 80 GB 16 GB M40 Low-CPU (R40) 80 GB 16 GB M40_NVME 380 GB 15.25 GB M50 160 GB 32 GB M50 Low-CPU (R50) 160 GB 32 GB M50_NVME 760 GB 30.5 GB M60 320 GB 64 GB M60 Low-CPU (R60) 320 GB 64 GB M60_NVME 1.6 TB 61 GB M80 760 GB 131 GB M80 Low-CPU (R80) 750 GB 122 GB M80_NVME 1.6 TB 122 GB M100 1 TB 160 GB M140 1 1 TB 192 GB M200 1.5 TB 256 GB M200 Low-CPU (R200) 1.5 TB 256 GB M200_NVME 3.1 TB 244 GB M300 1 2 TB 384 GB M300 Low-CPU (R300) 2 TB 384 GB M400 Low-CPU (R400) 3 TB 488 GB M400_NVME 2 4 TB 512 GB M700 Low-CPU (R700) 4 TB 768 GB - US_EAST_1
- US_EAST_2
- US_WEST_2
- EU_WEST_1
- EU_CENTRAL_1
- AP_NORTHEAST_1
NoteCluster Tier & API Naming ConventionsFor purposes of management with the Atlas API, cluster tier names that are prepended withR
instead of anM
(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 theproviderSettings.instanceSizeName
attribute.Workloads typically require less thanImportantMulti-Cloud Low-CPU clustersLow-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.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.
Amazon Availability Zones¶
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
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.
3AZ clusters have higher availability compared to 2AZ clusters. However, not all regions support 3AZ 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.
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 |