- Reference >
- Amazon Web Services
Amazon Web Services¶
Synopsis¶
Atlas supports deploying clusters onto Amazon Web Services (AWS). Atlas supports all AWS regions other than those in China and US GovCloud:
| AWS Region | Location |
|---|---|
us-east-1 |
US East (N. Virginia) |
us-east-2 |
US East (Ohio) |
us-west-1 |
US West (N. California) |
us-west-2 |
US West (Oregon) |
ca-central-1 |
Canada (Central) |
eu-west-1 |
EU (Ireland) |
eu-west-2 |
EU (London)” |
eu-central-1 |
EU (Frankfurt) |
ap-northeast-1 |
Asia Pacific (Tokyo) |
ap-northeast-2 |
Asia Pacific (Seoul) |
ap-southeast-1 |
Asia Pacific (Singapore) |
ap-southeast-2 |
Asia Pacific (Sydney) |
ap-south-1 |
Asia Pacific (Mumbai) |
sa-east-1 |
South America (Sao Paulo) |
This page provides reference material related to Atlas cluster deployments on AWS.
Instance Configuration Options¶
Each Atlas instance size 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 minimum custom storage size for all instances is
10GB.The maximum custom storage size for all instances is
4TB.Workloads typically require less than
2TB.- Custom Storage Speed
The input/output operations per second (IOPS) the system can perform. The available options depend on the specified storage size. Atlas provides the following custom storage speeds in order of maximum IOPS:
- Standard (Default)
- Fast
- Fastest.
Choosing the Fast or Fastest options changes the disk type from a general-purpose SSD to a provisioned-IOPS SSD [1].
The selected instance 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 instance. 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 affect 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] | (1, 2) For detailed documentation on Amazon storage options, see Amazon EBS Volume Types |