Vespa Cloud This content is applicable to Vespa Cloud deployments.

Zones

An application is deployed to a zone, which is a combination of an environment and a region, like vespa deploy -z dev.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 zones for development and performance testing:

EnvironmentDefaultRegionAWS Zone ID
devYesaws-us-east-1cuse1-az6
devNoaws-euw1-az1euw1-az1
devNoazure-eastus-az1
devNogcp-us-central1-f

prod zones for production serving, with a CD pipeline:

EnvironmentRegionAWS Zone ID
prodaws-us-east-1cuse1-az6
prodaws-use1-az4use1-az4
prodaws-use2-az1use2-az1
prodaws-use2-az3use2-az3
prodaws-us-west-2ausw2-az1
prodaws-usw2-az3usw2-az3
prodaws-eu-west-1aeuw1-az2
prodaws-euw1-az1euw1-az1
prodaws-euc1-az1euc1-az1
prodaws-euc1-az3euc1-az3
prodaws-cac1-az1cac1-az1
prodaws-cac1-az2cac1-az2
prodaws-ap-northeast-1aapne1-az4
prodaws-apne1-az1apne1-az1
prodgcp-europe-west3-b
prodgcp-us-central1-a
prodgcp-us-central1-b
prodgcp-us-central1-c
prodgcp-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:

EnvironmentRegionAWS Zone ID
testaws-us-east-1cuse1-az6
testgcp-us-central1-f
stagingaws-us-east-1cuse1-az6
staginggcp-us-central1-f

Contact Support to request more zones.