Endpoints: Vespa Cloud

By default all your Vespa application deployments will have an endpoint specific for the zone they are deployed in. In addition you can configure one or more global endpoint for the services in your application. This allows your application to support cross-zone failover.

*.z.vespa-app.cloud The endpoint for a deployment running in Zone
*.g.vespa-app.cloud A global endpoint as defined in deployment.xml

Zone endpoint

A zone endpoint has the format {service}.{instance}.{application}.{tenant}.{zone}.z.vespa-app.cloud.

service Optional The name of the Vespa service as defined in services.xml container id attribute. Can be omitted if the id is default.
instance Optional The name of the Vespa application instance as defined in deployment.xml. Can be omitted if the instance name is default.
application Mandatory The name of your application.
tenant Mandatory The name of your tenant.
zone Mandatory The zone you deployed your application in, as defined in deployment.xml.

Global endpoint

A global endpoint is an endpoint that can use all your deployments regardless of the zone which it is in. Using a global endpoint will allow for BCP support for your Vespa application.

A global endpoint has the format {name}.{instance}.{application}.{tenant}.g.vespa-app.cloud

Warning! Do not use global endpoints for feeding documents. Requests are sent to only one zone.

name Mandatory The name of the Vespa service as defined in services.xml container id attribute. Can be omitted if the id is default.
instance Optional The name of the Vespa application instance as defined in deployment.xml. Can be omitted if the instance name is default.
application Mandatory The name of your application.
tenant Mandatory The name of your tenant.