Vespa Cloud Enclave

Vespa Cloud Enclave allows Vespa Cloud applications to run inside the tenant’s own cloud accounts while everything is still fully managed by Vespa Cloud’s automation, giving the tenant full access to Vespa Cloud features inside their own cloud account. This allows tenant data to always remain within the bounds of services controlled by the tenant, and also to build closer integrations with Vespa applications inside the cloud services.

Vespa Cloud Enclave is available in AWS and GCP. Azure is on the roadmap.

Note: As the Vespa Cloud Enclave resources run in your account, this incurs resource costs from your cloud provider in addition to the Vespa Cloud costs.

AWS

• Getting started
• Architecture and security

GCP

• Getting started
• Architecture and security

Guides

• Operations and Support

FAQ

Which kind of permission is needed for the Vespa control plane to access my AWS accounts / GCP projects? The permissions required are coded into the Terraform modules found at:

• terraform-aws
• terraform-google

Navigate to the modules directory for details.