---
title: "Supported regions and instance types"
description: "Supported AWS regions, availability zones, and instance types available for Aerospike Cloud database clusters."
---

# Supported regions and instance types

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

Aerospike Cloud is available in specific AWS regions and their corresponding availability zones. Aerospike Cloud supports a variety of instance types to support your workloads.

::: tip
Aerospike can support additional regions or instance types upon request.
:::

## Supported AWS regions

The following table shows the AWS regions and availability zones where Aerospike Cloud is available. All regions support a minimum of three availability zones for high-availability deployments.

| Region | Region Name | Availability Zones | Zone Count |
| --- | --- | --- | --- |
| af-south-1 | Africa (Cape Town) | afs1-az1, afs1-az2, afs1-az3 | 3 |
| ap-east-1 | Asia Pacific (Hong Kong) | ape1-az1, ape1-az2, ape1-az3 | 3 |
| ap-east-2 | Asia Pacific (Taipei) | ape2-az1, ape2-az2, ape2-az3 | 3 |
| ap-northeast-1 | Asia Pacific (Tokyo) | apne1-az1, apne1-az2, apne1-az3, apne1-az4 | 4 |
| ap-northeast-2 | Asia Pacific (Seoul) | apne2-az1, apne2-az2, apne2-az3, apne2-az4 | 4 |
| ap-northeast-3 | Asia Pacific (Osaka) | apne3-az1, apne3-az2, apne3-az3 | 3 |
| ap-south-1 | Asia Pacific (Mumbai) | aps1-az1, aps1-az2, aps1-az3 | 3 |
| ap-south-2 | Asia Pacific (Hyderabad) | aps2-az1, aps2-az2, aps2-az3 | 3 |
| ap-southeast-1 | Asia Pacific (Singapore) | apse1-az1, apse1-az2, apse1-az3 | 3 |
| ap-southeast-2 | Asia Pacific (Sydney) | apse2-az1, apse2-az2, apse2-az3 | 3 |
| ap-southeast-3 | Asia Pacific (Jakarta) | apse3-az1, apse3-az2, apse3-az3 | 3 |
| ap-southeast-4 | Asia Pacific (Melbourne) | apse4-az1, apse4-az2, apse4-az3 | 3 |
| ap-southeast-5 | Asia Pacific (Malaysia) | apse5-az1, apse5-az2, apse5-az3 | 3 |
| ap-southeast-6 | Asia Pacific (New Zealand) | apse6-az1, apse6-az2, apse6-az3 | 3 |
| ap-southeast-7 | Asia Pacific (Thailand) | apse7-az1, apse7-az2, apse7-az3 | 3 |
| ca-central-1 | Canada (Central) | cac1-az1, cac1-az2, cac1-az4 | 3 |
| ca-west-1 | Canada West (Calgary) | caw1-az1, caw1-az2, caw1-az3 | 3 |
| eu-central-1 | Europe (Frankfurt) | euc1-az1, euc1-az2, euc1-az3 | 3 |
| eu-central-2 | Europe (Zurich) | euc2-az1, euc2-az2, euc2-az3 | 3 |
| eu-north-1 | Europe (Stockholm) | eun1-az1, eun1-az2, eun1-az3 | 3 |
| eu-south-1 | Europe (Milan) | eus1-az1, eus1-az2, eus1-az3 | 3 |
| eu-south-2 | Europe (Spain) | eus2-az1, eus2-az2, eus2-az3 | 3 |
| eu-west-1 | Europe (Ireland) | euw1-az1, euw1-az2, euw1-az3 | 3 |
| eu-west-2 | Europe (London) | euw2-az1, euw2-az2, euw2-az3 | 3 |
| eu-west-3 | Europe (Paris) | euw3-az1, euw3-az2, euw3-az3 | 3 |
| mx-central-1 | North America (Mexico City) | mxc1-az1, mxc1-az2, mxc1-az3 | 3 |
| sa-east-1 | South America (São Paulo) | sae1-az1, sae1-az2, sae1-az3 | 3 |
| us-east-1 | US East (N. Virginia) | use1-az1, use1-az2, use1-az3, use1-az4, use1-az5, use1-az6 | 6 |
| us-east-2 | US East (Ohio) | use2-az1, use2-az2, use2-az3 | 3 |
| us-west-2 | US West (Oregon) | usw2-az1, usw2-az2, usw2-az3, usw2-az4 | 4 |

## Supported AWS instance types

The following table shows the AWS instance types you can use when provisioning an Aerospike Cloud database cluster.

| Instance Family | Description | Regions Available |
| --- | --- | --- |
| **i3en** | Storage optimized with NVMe SSD (Intel, high density) | af-south-1, ap-east-1, ap-east-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ap-southeast-6, ap-southeast-7, ca-central-1, ca-west-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-2, eu-west-3, mx-central-1, sa-east-1 |
| **i4g** | Storage optimized with NVMe SSD (Graviton2) | ap-southeast-1, ap-southeast-2, ca-central-1, eu-west-1, sa-east-1, us-east-1, us-east-2, us-west-2 |
| **i4i** | Storage optimized with NVMe SSD (Intel) | All regions |
| **i7i** | Storage optimized with NVMe SSD (4th gen Intel) | af-south-1, ap-east-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ca-central-1, ca-west-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-2, sa-east-1 |
| **i7ie** | Storage optimized with NVMe SSD (4th gen Intel, extended) | af-south-1, ap-northeast-1, ap-southeast-3, ap-southeast-5, ca-central-1, ca-west-1, eu-north-1, eu-south-2, eu-west-2, eu-west-3, sa-east-1 |
| **i8g** | Storage optimized with NVMe SSD (ARM-based Graviton4) | ap-northeast-1, ap-northeast-2, ap-northeast-3, ca-central-1, eu-north-1, eu-south-2, eu-west-2, sa-east-1 |
| **is4gen** | Storage optimized with NVMe SSD (Graviton2) | ap-northeast-1, ca-central-1, eu-west-2, eu-west-3 |
| **m5d** | General purpose with local NVMe (Intel) | af-south-1, ap-east-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ap-southeast-3, ap-southeast-4, ca-central-1, ca-west-1, eu-central-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-east-2, us-west-2 |
| **m6gd** | General purpose with local NVMe (Graviton2) | af-south-1, ap-east-1, ap-east-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ap-southeast-6, ap-southeast-7, ca-central-1, ca-west-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-2, eu-west-3, mx-central-1, sa-east-1 |
| **m7gd** | General purpose with local NVMe (Graviton3) | ap-east-2, ap-northeast-1, ap-northeast-2, ap-southeast-5, ap-southeast-6, ap-southeast-7, eu-north-1, eu-south-2, eu-west-3, mx-central-1, sa-east-1 |
| **m8gd** | General purpose with local NVMe (Graviton4) | ap-northeast-1, ap-southeast-5, ca-central-1, eu-south-2, eu-west-2, sa-east-1 |
| **r6gd** | Memory optimized with local NVMe (Graviton2) | af-south-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-southeast-1, ap-southeast-2, ap-southeast-3, ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-east-2, us-west-2 |
| **r7g** | Memory optimized (ARM-based Graviton3) | af-south-1, ap-east-1, ap-east-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ap-southeast-6, ap-southeast-7, ca-central-1, ca-west-1, eu-central-2, eu-north-1, eu-south-1, eu-south-2, eu-west-2, eu-west-3, mx-central-1, sa-east-1 |
| **r7gd** | Memory optimized with local NVMe (Graviton3) | af-south-1, ap-east-1, ap-east-2, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-south-2, ap-southeast-1, ap-southeast-2, ap-southeast-3, ap-southeast-5, ap-southeast-6, ap-southeast-7, eu-central-1, eu-north-1, eu-south-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, mx-central-1, us-east-1, us-east-2, us-west-2 |
| **r8g** | Memory optimized (ARM-based Graviton4) | ap-east-1, ap-northeast-1, ap-northeast-2, ap-northeast-3, ap-south-1, ap-south-2, ap-southeast-2, ap-southeast-3, ap-southeast-4, ap-southeast-5, ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-south-2, eu-west-1, eu-west-2, eu-west-3, mx-central-1, sa-east-1, us-east-1, us-east-2, us-west-2 |
| **r8gd** | Memory optimized with local NVMe (Graviton4) | ap-northeast-1, ap-southeast-5, ca-central-1, eu-south-2, eu-west-2, sa-east-1 |
| **t4g** | Burstable general purpose (ARM-based Graviton2) | ap-east-2, ap-southeast-5, ap-southeast-6, ap-southeast-7, mx-central-1 |
| **x8g** | Memory optimized (Graviton4, high memory) | eu-north-1 |

::: caution
AWS does not guarantee availability of specific instance types. Aerospike Cloud does not currently reserve instance capacity for every instance type and cannot guarantee immediate availability of your requested instance type. The healthy provisioning of a cluster depends on how long it takes for AWS to supply the requested instance type.  
  
If you find a cluster is taking too long to provision, you can decommission it and select a different instance type. Common families like _i4i_ and _r7g_ tend to have more availability, and you can often achieve similar cluster optimizations with a different configuration. Your account manager can help you size your cluster appropriately.
:::