Amazon Web Services (AWS)
On this page
Atlas supports deploying clusters and serverless instances 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
M10+ clusters, some regions
M2/M5 clusters, or
serverless instances. A check mark indicates support for
M2/M5 clusters, or serverless instances. The Atlas
Region is the corresponding region name used by the Atlas API.
This page provides reference material related to Atlas cluster deployments on AWS. The following options do not apply to serverless instances.
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 .
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 RAMM0.5 GBSharedM22 GBSharedM55 GBSharedM1010 GB2 GBM2020 GB4 GBM3040 GB8 GBM4080 GB16 GBR4080 GB16 GBM40_NVME380 GB15.25 GBM50160 GB32 GBR50160 GB32 GBM50_NVME760 GB30.5 GBM60320 GB64 GBR60320 GB64 GBM60_NVME1.6 TB61 GBM80760 GB131 GBR80750 GB122 GBM80_NVME1.6 TB122 GBM1001 TB160 GBM1401 TB192 GBM2001.5 TB256 GBR2001.5 TB256 GBM200_NVME3.1 TB244 GBM3002 TB384 GBR3002 TB384 GBR4003 TB488 GBM400_NVME4 TB512 GBR7004 TB768 GB
Can use this tier for a multi-cloud cluster.
Unavailable in the AP_SOUTHEAST_2 region.
Cluster Tier & API Naming Conventions
For purposes of management with the Atlas Administration API, cluster tier names that are prepended with
Rinstead of an
R40for 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
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
- 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.
|||For detailed documentation on Amazon storage options, see Amazon EBS Volume Types|
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.
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
AWS EventBridge: Send Atlas trigger events to AWS EventBridge
Amazon Kinesis: Send data to Atlas via Kinesis Data Firehose
AWS S3: Configure Atlas Data Federation to query data from S3
AWS Marketplace: Pay for Atlas usage via AWS
For more information on how to use AWS with Atlas most effectively, review the following best practices, guides, and case studies: