> 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/configuration-reference/environment-variables.md).

# Environment variables

Environment variables used in an e6data In-VPC deployment and by client connectors.

Environment variables appear in two places: the In-VPC deployment commands, and client-side connector configuration.

## Deployment variables (In-VPC)

The In-VPC deployment commands reference these from your environment as you work through the build. The common ones:

| Variable                                                                              | Description                                              |
| ------------------------------------------------------------------------------------- | -------------------------------------------------------- |
| `WORKSPACE_NAME`                                                                      | The workspace name (also the Kubernetes namespace)       |
| `TENANT_NAME`                                                                         | Your tenant identifier (from onboarding)                 |
| `CLUSTER_NAME`                                                                        | Your Kubernetes cluster name                             |
| `REGION` / `LOCATION`                                                                 | Cloud region                                             |
| `RESOURCE_GROUP`                                                                      | (Azure) Resource group                                   |
| `SUBSCRIPTION_ID`                                                                     | (Azure) Azure subscription ID                            |
| `AWS_ACCOUNT_ID`                                                                      | (AWS) Your AWS account ID                                |
| `AZURE_STORAGE_ACCOUNT_NAME` / `STORAGE_ACCOUNT`                                      | (Azure) ADLS Gen2 account for metadata                   |
| `AGENT_API_BASE_URL`                                                                  | Control plane URL the console polls (from onboarding)    |
| `AUTHZ_SUPER_ADMINS`                                                                  | Comma-separated super-admin emails for the console       |
| `JWT_ISSUER` / `JWT_JWKS_URI` / `JWT_AUDIENCE`                                        | Auth configuration for the QueryRouter (from onboarding) |
| `GREPTIME_ENDPOINT` / `GREPTIME_DATABASE` / `GREPTIME_USERNAME` / `GREPTIME_PASSWORD` | Monitoring credentials (if enabled)                      |

See the In-VPC deployment guides for [AWS](/query-engine/guides/deployment/aws-in-vpc/deploy-workspace-and-e6data.md) and [Azure](/query-engine/guides/deployment/azure-in-vpc/deploy-workspace-and-e6data.md).

## Client connector variables

When connecting from scripts, CI, or applications, keep credentials out of source by reading them from the environment. Common conventions used in the examples:

| Variable                                              | Used by                                         |
| ----------------------------------------------------- | ----------------------------------------------- |
| `E6DATA_TOKEN`                                        | A personal access token for REST/driver scripts |
| `E6DATA_API_KEY` / `E6DATA_SERVICE_ACCOUNT_KEY`       | A service account key for CI/automation         |
| `E6DATA_HOST`                                         | The workspace endpoint host                     |
| `E6DATA_USERNAME`                                     | Your e6data email                               |
| `E6DATA_DATABASE`, `E6DATA_CATALOG`, `E6DATA_CLUSTER` | Target database, catalog, and cluster           |

These names are conventions in the example code, not fixed by the platform - use whatever your tooling expects, but never hardcode token values. See [Token security best practices](/query-engine/guides/security/access-tokens/token-security-best-practices.md).

## See also

* [Helm values](/query-engine/reference/configuration-reference/helm-values.md)
* [Connecting to the engine](/query-engine/developers/connecting-to-the-engine.md)
* [Management API](/query-engine/developers/management-api.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/configuration-reference/environment-variables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.