Regions and quotas
The AWS regions a default installation can run in, the regional constraints of the services it uses, and the AWS quotas to raise before the first deploy.
An installation runs in one AWS account and one region. The default features use services that AWS offers in fewer regions than the rest of the stack. Check every row below for your region before you install.
Regional constraints
| Service | Used by | Constraint |
|---|---|---|
| AWS Lambda MicroVMs | The sandbox, on every deploy | Available in 10 regions as of August 2026: us-east-1, us-east-2, us-west-2, eu-west-1, eu-central-1, eu-north-1, ap-northeast-1, ap-south-1, ap-southeast-1, and ap-southeast-2. The platform-customer profile publishes and verifies a MicroVM image on every deploy. In another region, set "lambdaMicrovm": false in the deployment target; the tool then skips those steps and turns the sandbox off, so agents have no sandbox tools. |
| Amazon Bedrock | Default chat and embedding models | The defaults are global cross-Region inference profiles, global.anthropic.claude-haiku-4-5-20251001-v1:0 and global.cohere.embed-v4:0. Your region must be a source region of both profiles. The model gateway and catalog sync call Bedrock only in the installation region. |
| Amazon SES receiving | Agent email | The active receipt rule set and the inbound-smtp.<region>.amazonaws.com MX record need a region where SES supports email receiving. See the email receiving endpoints. |
| Amazon SES sending | Sign-in and agent email | Production access is granted per region. |
| CloudFront certificates | Console, apps, stream gateway edge | Must be in us-east-1. The root configures a second AWS provider for it. |
| Graviton instance types | OpenSearch, NAT instance, ClickHouse | m7g.large.search, t4g.small, and t4g.medium must exist in the region. Override network_nat_instance_type or agent_observability_clickhouse_instance_type where they do not. |
| fck-nat AMI | NAT instance | The root looks up the publisher's ARM64 AL2023 AMI in the installation region; the publisher must offer one there, or set network_nat_instance_ami_id. |
| Ubuntu 24.04 ARM64 AMI | ClickHouse node | The hot-plane module looks up Canonical's newest Ubuntu 24.04 ARM64 AMI in the installation region at the first apply; Canonical must publish one there, or set agent_observability_clickhouse_ami_id. |
Check the AWS regional service lists for every row before you choose a region.
Quotas
| Quota | What the default installation needs |
|---|---|
| Lambda concurrent executions | A new account can start with as few as 10. The platform reserves 150: 100 for the public API, 20 for the identity API, 20 for the agent runtime API, and 10 for webhook delivery. Request at least 1,000 before the first deploy. |
| Elastic IP addresses | One for the NAT instance, or one per availability zone with NAT gateways. |
| VPCs and NAT gateways | One VPC. NAT gateways only in gateway mode, one per zone. |
| OpenSearch instances | Four m7g.large.search instances across two domains, or two with shared_search_domain. |
| Fargate vCPUs | About 8.25 vCPUs at the sample posture's minimum task counts, rising as the agent worker scales to 20 tasks of 1 vCPU. |
| EC2 On-Demand vCPUs | Four Standard-family vCPUs: two for the t4g.small NAT instance and two for the t4g.medium ClickHouse node. |
| Bedrock tokens per minute | The account's per-model quotas for the two default models bound how much agents and memory can call them. |
| SES sending quota | Granted with production access, per region. |
Troubleshooting covers the errors a first deploy shows when a quota is too low.