Amazon Web Services (AWS)
On this page
- Cluster Configuration Options
- Amazon Availability Zones
- Regions with at Least Three Availability Zones
- Regions with Only Two Availability Zones
- Dedicated Search Nodes
- Supported Regions
- Available Search Tiers
- Stream Processing Instances
- Integrations
- Networking Services
- Security and Identity Services
- Other AWS Services
- Procurement
- More Information
Atlas supports deploying clusters onto Amazon Web Services (AWS). Atlas supports all AWS regions other than some regions in China and US GovCloud.
Atlas supports the following AWS regions. While all of the
following regions support dedicated clusters (M10+
),
some regions don't support free and Atlas Flex clusters.
The Atlas API uses the corresponding
Atlas Region.
AWS Region | Location | Atlas Region | M0/M2/M5/Atlas Flex Support | M10+ Support |
---|---|---|---|---|
| Northern Virginia, USA |
| ||
| Oregon, USA |
| ||
| Montreal, QC, Canada |
| ||
| Calgary, Canada |
| ||
| Ohio, USA |
| ||
| Northern California, USA |
| ||
| Sao Paulo, Brazil |
|
AWS Region | Location | Atlas Region | M0/M2/M5/Atlas Flex Support | M10+ Support |
---|---|---|---|---|
| Singapore |
| ||
| Sydney, NSW, Australia |
| ||
| Jakarta, Indonesia |
| ||
| Mumbai, India |
| ||
| Hong Kong, China |
| ||
| Tokyo, Japan |
| ||
| Seoul, South Korea |
| ||
| Osaka, Japan |
| ||
| Hyderabad, India |
| ||
| Melbourne, Victoria, Australia |
|
AWS Region | Location | Atlas Region | M0/M2/M5/Atlas Flex Support | M10+ Support |
---|---|---|---|---|
| Ireland |
| ||
| Frankfurt, Germany |
| ||
| Stockholm, Sweden |
| ||
| London, England, UK |
| ||
| Paris, France |
| ||
| Milan, Italy |
| ||
| Zurich, Switzerland |
| ||
| Spain |
|
AWS Region | Location | Atlas Region | M0/M2/M5/Atlas Flex Support | M10+ Support |
---|---|---|---|---|
| Bahrain |
| ||
| Cape Town, South Africa |
| ||
| Tel Aviv, Israel |
| ||
| UAE |
|
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].
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 SizeStorage RangeDefault StorageDefault RAMM0
.5 GB
.5 GB
Shared
M2
2 GB
2 GB
Shared
M5
5 GB
5 GB
Shared
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
R40
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
R50
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
R60
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
R80
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
R200
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
R300
10 GB to 4 TB
2 TB
384 GB
R400
10 GB to 4 TB
3 TB
488 GB
M400_NVME
4 TB
4 TB
512 GB
R700
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.
Note
Cluster Tier & API Naming Conventions
For purposes of management with the Atlas Administration API, cluster tier names that are prepended with
R
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.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.
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 |
Dedicated Search Nodes
Supported Regions
Atlas supports deploying separate Search Nodes for M10
and higher
clusters in the following AWS regions:
AWS Region | Location | Atlas Region |
---|---|---|
| Northern Virginia, USA |
|
| Oregon, USA |
|
| Montreal, QC, Canada |
|
| Ohio, USA |
|
| Northern California, USA |
|
| Sao Paulo, Brazil |
|
AWS Region | Location | Atlas Region |
---|---|---|
| Singapore |
|
| Sydney, NSW, Australia |
|
| Mumbai, India |
|
| Tokyo, Japan |
|
| Seoul, South Korea |
|
| Osaka, Japan |
|
AWS Region | Location | Atlas Region |
---|---|---|
| Ireland |
|
| Frankfurt, Germany |
|
| Stockholm, Sweden |
|
| London, England, UK |
|
| Paris, France |
|
Available Search Tiers
Atlas provides different search tiers for Search Nodes deployed on AWS depending on the selected region. The following table shows the search tiers and the regions where the search tiers are available for each class of hardware, low-CPU or high-CPU:
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S80 |
|
|
|
S90 |
|
|
|
S100 |
|
|
|
S110 |
|
|
|
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S20 |
|
|
|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S70 |
|
|
|
S80 |
|
|
|
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S80 |
|
|
|
S90 |
|
|
|
S100 |
|
|
|
S110 |
|
|
|
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S20 |
|
|
|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S70 |
|
|
|
S80 |
|
|
|
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S70 |
|
|
|
S80 |
|
|
|
S90 |
|
|
|
S100 |
|
|
|
S110 |
|
|
|
Instance Size | Instance Details | AWS Region | Location |
---|---|---|---|
S20 |
|
|
|
S30 |
|
|
|
S40 |
|
|
|
S50 |
|
|
|
S60 |
|
|
|
S70 |
|
|
|
S80 |
|
|
|
Stream Processing Instances
Atlas supports deploying Stream Processing Instances in the follow AWS regions:
AWS Region | Location | Atlas Region |
---|---|---|
| Northern Virginia, USA |
|
| Oregon, USA |
|
| Montreal, QC, Canada |
|
| Sao Paulo, Brazil |
|
AWS Region | Location | Atlas Region |
---|---|---|
| Singapore |
|
| Sydney, NSW, Australia |
|
| Mumbai, India |
|
| Tokyo, Japan |
|
AWS Region | Location | Atlas Region |
---|---|---|
| Ireland |
|
| Frankfurt, Germany |
|
| London, England, UK |
|
Integrations
Along with global region support, the following product integrations enable applications running on AWS, 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
AWS Virtual Private Cloud (VPC): Set up network peering connections with AWS
Security and Identity Services
AWS Identity Access Management (IAM) Configure database users with IAM authentication
AWS Key Management Service (KMS):
AWS SSO: Configure federated authentication to the MongoDB UI
Other AWS Services
AWS CloudFormation: Deploy and manage Atlas from CloudFormation
Amazon EventBridge: Send Atlas trigger events to Amazon EventBridge
Amazon Kinesis: Send data to Atlas via Kinesis Data Firehose
AWS S3: Configure Atlas Data Federation to query data from S3
Procurement
AWS Marketplace: Pay for Atlas usage via AWS
More Information
For more information on how to use AWS with Atlas most effectively, review the following best practices, guides, and case studies: