Services and dependencies - e6data Docs

This section covers where e6data is available and what external services it depends on.

Supported regions

Cloud	Page
AWS	AWS regions
Azure	Azure regions

For Serverless deployments, your workspace runs in the region you select at creation. For In-VPC deployments, the region is determined by where your Kubernetes cluster runs. If your preferred region isn’t listed, contact e6data support - new regions are added based on customer demand.

External dependencies

e6data depends on a small set of external services. All are accessed only by e6data’s infrastructure, not your environment, unless specifically noted.

Dependency	Purpose	Where it runs
Public CA (Let’s Encrypt or similar)	TLS certificates for endpoints	External
Cloud provider APIs	Provisioning compute and storage	The cloud you’re deployed on
Container registry	Component images	e6data-hosted (Serverless) or your cluster’s pull source (In-VPC)
OpenTelemetry endpoints	Customer-configured for observability	Customer-managed

Network egress

For In-VPC deployments, your cluster’s outbound network requirements are listed in the cloud-specific setup guide:

See also

Last modified on October 1, 2026