> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/services-and-dependencies.md).

# Services and dependencies

Supported cloud regions and external dependencies for e6data deployments.

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

## Supported regions

| Cloud | Page                                                                                |
| ----- | ----------------------------------------------------------------------------------- |
| AWS   | [AWS regions](/query-engine/reference/services-and-dependencies/aws-regions.md)     |
| Azure | [Azure regions](/query-engine/reference/services-and-dependencies/azure-regions.md) |

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:

* [Azure In-VPC prerequisites](/query-engine/guides/deployment/azure-in-vpc/prerequisites.md)
* AWS In-VPC prerequisites (coming soon)

## See also

* [Choose a setup path](/query-engine/get-started/quickstart/choose-setup-path.md)
* [Limitations](/query-engine/reference/limitations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.e6data.com/query-engine/reference/services-and-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.