An application is deployed to a zone,
which is a combination of an environment and a region,
like vespa deploy -z perf.aws-us-east-1c.
If an application requires zone-specific configuration (e.g., different capacity requirements per zone), use environment and region variants. Also see deployment.xml.
dev and perf zones for development and performance testing:
| Environment | Region |
|---|---|
| dev | aws-us-east-1c |
| dev | aws-euw1-az1 |
| dev | azure-eastus-az1 |
| dev | gcp-us-central1-f |
| perf | aws-us-east-1c |
prod zones for production serving,
with a CD pipeline:
| Environment | Region |
|---|---|
| prod | aws-us-east-1c |
| prod | aws-use1-az4 |
| prod | aws-use2-az1 |
| prod | aws-use2-az3 |
| prod | aws-us-west-2a |
| prod | aws-eu-central-1a |
| prod | aws-eu-west-1a |
| prod | aws-ap-northeast-1a |
| prod | gcp-europe-west3-b |
| prod | gcp-us-central1-a |
| prod | gcp-us-central1-f |
The prod zones use ephemeral instances for system tests and staging tests,
running in test and
staging environments.
These are internal zones, and never directly deployed to, included here for reference:
| Environment | Region |
|---|---|
| test | aws-us-east-1c |
| test | gcp-us-central1-f |
| staging | aws-us-east-1c |
| staging | gcp-us-central1-f |
Contact Support to request more zones.