> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported regions and availability zones

Managed BYOC runs in AWS commercial regions where every AWS service and instance type it uses is available. The control plane and data planes use different services, so each has its own list of supported regions. A data plane can run in a different region from your control plane.

GovCloud, China, and the AWS European Sovereign Cloud aren't supported.

## Control plane regions

| Region | Location | Opt-in region |
| - | - | - |
| `us-east-1` | US East (N. Virginia) | No |
| `us-east-2` | US East (Ohio) | No |
| `us-west-2` | US West (Oregon) | No |
| `ap-south-1` | Asia Pacific (Mumbai) | No |
| `ap-southeast-1` | Asia Pacific (Singapore) | No |
| `ap-southeast-2` | Asia Pacific (Sydney) | No |
| `ap-northeast-1` | Asia Pacific (Tokyo) | No |
| `eu-central-1` | Europe (Frankfurt) | No |
| `eu-west-1` | Europe (Ireland) | No |
| `eu-west-2` | Europe (London) | No |
| `eu-west-3` | Europe (Paris) | No |
| `eu-north-1` | Europe (Stockholm) | No |
| `eu-south-1` | Europe (Milan) | Yes |

## Data plane regions

| Region | Location | Opt-in region |
| - | - | - |
| `us-east-1` | US East (N. Virginia) | No |
| `us-east-2` | US East (Ohio) | No |
| `us-west-1` | US West (N. California) | No |
| `us-west-2` | US West (Oregon) | No |
| `ca-central-1` | Canada (Central) | No |
| `sa-east-1` | South America (São Paulo) | No |
| `eu-central-1` | Europe (Frankfurt) | No |
| `eu-central-2` | Europe (Zurich) | Yes |
| `eu-west-1` | Europe (Ireland) | No |
| `eu-west-2` | Europe (London) | No |
| `eu-west-3` | Europe (Paris) | No |
| `eu-south-2` | Europe (Spain) | Yes |
| `eu-north-1` | Europe (Stockholm) | No |
| `il-central-1` | Israel (Tel Aviv) | Yes |
| `me-south-1` | Middle East (Bahrain) | Yes |
| `me-central-1` | Middle East (UAE) | Yes |
| `af-south-1` | Africa (Cape Town) | Yes |
| `ap-east-1` | Asia Pacific (Hong Kong) | Yes |
| `ap-south-1` | Asia Pacific (Mumbai) | No |
| `ap-south-2` | Asia Pacific (Hyderabad) | Yes |
| `ap-southeast-1` | Asia Pacific (Singapore) | No |
| `ap-southeast-2` | Asia Pacific (Sydney) | No |
| `ap-southeast-3` | Asia Pacific (Jakarta) | Yes |
| `ap-southeast-4` | Asia Pacific (Melbourne) | Yes |
| `ap-southeast-5` | Asia Pacific (Malaysia) | Yes |
| `ap-southeast-6` | Asia Pacific (New Zealand) | Yes |
| `ap-southeast-7` | Asia Pacific (Thailand) | Yes |
| `ap-northeast-1` | Asia Pacific (Tokyo) | No |
| `ap-northeast-2` | Asia Pacific (Seoul) | No |
| `ap-northeast-3` | Asia Pacific (Osaka) | No |

Turn on an opt-in region in your AWS account before Superblocks deploys there.

## Availability zones

Each VPC uses at least two availability zones, identified by AZ ID, such as `usw2-az1`. We recommend three for the control plane.

A few AZ IDs can't hold the subnets Managed BYOC uses. Don't use these zones for that part of your instance:

| Region | AZ ID | Not supported for | Reason |
| - | - | - | - |
| `us-east-1` | `use1-az3` | Control plane and data planes | Amazon EKS can't place cluster network interfaces in it, and Amazon Bedrock AgentCore doesn't support it |
| `us-east-1` | `use1-az5` | Control plane agent subnets | Amazon Bedrock AgentCore doesn't support it |
| `us-west-1` | `usw1-az2` | Data planes | Amazon EKS and AWS Global Accelerator don't support it |
| `us-west-2` | `usw2-az4` | Control plane agent subnets | Amazon Bedrock AgentCore doesn't support it |
| `ca-central-1` | `cac1-az3` | Data planes | Amazon EKS and AWS Global Accelerator don't support it |
| `ap-northeast-1` | `apne1-az3` | Data planes and control plane agent subnets | AWS Global Accelerator and Amazon Bedrock AgentCore don't support it |
| `eu-west-2` | `euw2-az4` | Control plane agent subnets | Amazon Bedrock AgentCore doesn't support it |

Agent subnets only need two zones that AgentCore supports, so the rest of the control plane can still use a zone that's excluded only for agent subnets.

Newer AWS accounts have access to only two availability zones in `us-west-1`. If one of yours is `usw1-az2`, a data plane in `us-west-1` can't meet the two-zone minimum. Check your account's AZ IDs before choosing that region.

## Related

* [Managed BYOC deployment guide](https://docs.superblocks.com/enterprise/cloud-prem/deployment-guide.md)
* [Managed BYOC on AWS](https://docs.superblocks.com/enterprise/cloud-prem/aws.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.