Docs Menu
Docs Home
/
MongoDB Atlas
/ /

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

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

ca-west-1

Calgary, Canada

CA_WEST_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

AWS Region
Location
Atlas Region
M0/M2/M5/Atlas Flex Support
M10+ Support

ap-southeast-1

Singapore

AP_SOUTHEAST_1

ap-southeast-2

Sydney, NSW, Australia

AP_SOUTHEAST_2

ap-southeast-3

Jakarta, Indonesia

AP_SOUTHEAST_3

ap-south-1

Mumbai, India

AP_SOUTH_1

ap-east-1

Hong Kong, China

AP_EAST_1

ap-northeast-1

Tokyo, Japan

AP_NORTHEAST_1

ap-northeast-2

Seoul, South Korea

AP_NORTHEAST_2

ap-northeast-3

Osaka, Japan

AP_NORTHEAST_3

ap-south-2

Hyderabad, India

AP_SOUTH_2

ap-southeast-4

Melbourne, Victoria, Australia

AP_SOUTHEAST_4

AWS Region
Location
Atlas Region
M0/M2/M5/Atlas Flex Support
M10+ Support

eu-west-1

Ireland

EU_WEST_1

eu-central-1

Frankfurt, Germany

EU_CENTRAL_1

eu-north-1

Stockholm, Sweden

EU_NORTH_1

eu-west-2

London, England, UK

EU_WEST_2

eu-west-3

Paris, France

EU_WEST_3

eu-south-1

Milan, Italy

EU_SOUTH_1

eu-central-2

Zurich, Switzerland

EU_CENTRAL_2

eu-south-2

Spain

EU_SOUTH_2

AWS Region
Location
Atlas Region
M0/M2/M5/Atlas Flex Support
M10+ Support

me-south-1

Bahrain

ME_SOUTH_1

af-south-1

Cape Town, South Africa

AF_SOUTH_1

il-central-1

Tel Aviv, Israel

IL_CENTRAL_1

me-central-1

UAE

ME_CENTRAL_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].

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 Size
Storage Range
Default Storage
Default RAM

M0

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

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.
click to enlarge

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.
click to enlarge

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

Atlas supports deploying separate Search Nodes for M10 and higher clusters in the following AWS regions:

AWS Region
Location
Atlas Region

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

AWS Region
Location
Atlas Region

ap-southeast-1

Singapore

AP_SOUTHEAST_1

ap-southeast-2

Sydney, NSW, Australia

AP_SOUTHEAST_2

ap-south-1

Mumbai, India

AP_SOUTH_1

ap-northeast-1

Tokyo, Japan

AP_NORTHEAST_1

ap-northeast-2

Seoul, South Korea

AP_NORTHEAST_2

ap-northeast-3

Osaka, Japan

AP_NORTHEAST_3

AWS Region
Location
Atlas Region

eu-west-1

Ireland

EU_WEST_1

eu-central-1

Frankfurt, Germany

EU_CENTRAL_1

eu-north-1

Stockholm, Sweden

EU_NORTH_1

eu-west-2

London, England, UK

EU_WEST_2

eu-west-3

Paris, France

EU_WEST_3

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

  • Default RAM: 8 GB

  • Default Storage: 50 GB

  • vCPU: 1

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S40

  • Default RAM: 16 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S50

  • Default RAM: 32 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S60

  • Default RAM: 64 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S80

  • Default RAM: 128 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S90

  • Default RAM: 256 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S100

  • Default RAM: 384 GB

  • Default Storage: 2400 GB

  • vCPU: 64

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S110

  • Default RAM: 512 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

Instance Size
Instance Details
AWS Region
Location

S20

  • Default RAM: 4 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S30

  • Default RAM: 8 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S40

  • Default RAM: 16 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S50

  • Default RAM: 32 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S60

  • Default RAM: 64 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S70

  • Default RAM: 96 GB

  • Default Storage: 2400 GB

  • vCPU: 48

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

S80

  • Default RAM: 128 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • us-east-1

  • us-east-2

  • us-west-1

  • us-west-2

  • ca-central-1

  • sa-east-1

  • Northern Virginia, USA

  • Ohio, USA

  • Northern California, USA

  • Oregon, USA

  • Montreal, QC, Canada

  • Sao Paulo, Brazil

Instance Size
Instance Details
AWS Region
Location

S30

  • Default RAM: 8 GB

  • Default Storage: 50 GB

  • vCPU: 1

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S40

  • Default RAM: 16 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S50

  • Default RAM: 32 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S60

  • Default RAM: 64 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S80

  • Default RAM: 128 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S90

  • Default RAM: 256 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S100

  • Default RAM: 384 GB

  • Default Storage: 2400 GB

  • vCPU: 64

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S110

  • Default RAM: 512 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

Instance Size
Instance Details
AWS Region
Location

S20

  • Default RAM: 4 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S30

  • Default RAM: 8 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S40

  • Default RAM: 16 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S50

  • Default RAM: 32 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S60

  • Default RAM: 64 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S70

  • Default RAM: 96 GB

  • Default Storage: 2400 GB

  • vCPU: 48

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

S80

  • Default RAM: 128 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • ap-southeast-1

  • ap-southeast-2

  • ap-south-1

  • ap-northeast-1

  • ap-northeast-2

  • ap-northeast-3

  • Singapore

  • Sydney, NSW, Australia

  • Mumbai, India

  • Tokyo, Japan

  • Seoul, South Korea

  • Osaka, Japan

Instance Size
Instance Details
AWS Region
Location

S30

  • Default RAM: 8 GB

  • Default Storage: 50 GB

  • vCPU: 1

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S40

  • Default RAM: 16 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S50

  • Default RAM: 32 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S60

  • Default RAM: 64 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S70

  • Default RAM: 96 GB

  • Default Storage: 2400 GB

  • vCPU: 48

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S80

  • Default RAM: 128 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S90

  • Default RAM: 256 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S100

  • Default RAM: 384 GB

  • Default Storage: 2400 GB

  • vCPU: 64

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S110

  • Default RAM: 512 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

Instance Size
Instance Details
AWS Region
Location

S20

  • Default RAM: 4 GB

  • Default Storage: 100 GB

  • vCPU: 2

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S30

  • Default RAM: 8 GB

  • Default Storage: 200 GB

  • vCPU: 4

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S40

  • Default RAM: 16 GB

  • Default Storage: 380 GB

  • vCPU: 8

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S50

  • Default RAM: 32 GB

  • Default Storage: 760 GB

  • vCPU: 16

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S60

  • Default RAM: 64 GB

  • Default Storage: 1600 GB

  • vCPU: 32

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S70

  • Default RAM: 96 GB

  • Default Storage: 2400 GB

  • vCPU: 48

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

S80

  • Default RAM: 128 GB

  • Default Storage: 3200 GB

  • vCPU: 64

  • eu-west-1

  • eu-west-2

  • eu-central-1

  • eu-north-1

  • Ireland

  • London, England, UK

  • Frankfurt, Germany

  • Stockholm, Sweden

Atlas supports deploying Stream Processing Instances in the follow AWS regions:

AWS Region
Location
Atlas Region

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

sa-east-1

Sao Paulo, Brazil

SA_EAST_1

AWS Region
Location
Atlas Region

ap-southeast-1

Singapore

AP_SOUTHEAST_1

ap-southeast-2

Sydney, NSW, Australia

AP_SOUTHEAST_2

ap-south-1

Mumbai, India

AP_SOUTH_1

ap-northeast-1

Tokyo, Japan

AP_NORTHEAST_1

AWS Region
Location
Atlas Region

eu-west-1

Ireland

EU_WEST_1

eu-central-1

Frankfurt, Germany

EU_CENTRAL_1

eu-west-2

London, England, UK

EU_WEST_2

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.

For more information on how to use AWS with Atlas most effectively, review the following best practices, guides, and case studies:

Back

Cloud Providers