> 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/guides/guides.md).

# Overview

Task-based guides for deploying, securing, connecting, and operating e6data - from workspace setup to querying.

How-to guides for setting up and running e6data day to day. Start with Deployment if you're standing up a workspace; otherwise jump to the area you need.

## What's here

| Area                                                                                  | What it covers                                                    |
| ------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| [Deployment](/query-engine/guides/deployment/aws-serverless.md)                       | Stand up a workspace on AWS or Azure, Serverless or In Your VPC   |
| [Workspaces](/query-engine/guides/workspaces.md)                                      | Create, configure, and delete workspaces                          |
| [Security](/query-engine/guides/security/identity-and-rbac.md)                        | Identity, RBAC, access tokens, and SSO                            |
| [Network access](broken://pages/Wh4d9jql2OPH1ux7JE4O)                                 | Endpoints, IP sets, and firewall rules                            |
| [Catalogs](/query-engine/guides/catalogs.md)                                          | Connect metastores - Hive, Glue, Unity, Fabric, Polaris, and more |
| [Table formats](/query-engine/guides/table-formats.md)                                | Query Iceberg, Delta Lake, and Hive tables                        |
| [Data governance](/query-engine/guides/data-governance.md)                            | Catalog-level access control and data access policies             |
| [Clusters](/query-engine/guides/clusters/create-and-manage-clusters.md)               | Create, size, scale, and upgrade the compute that runs queries    |
| [Querying](/query-engine/guides/querying/query-editor.md)                             | Run queries in the SQL Editor and work with results               |
| [Operations](/query-engine/guides/operations/upgrades-and-releases.md)                | Upgrades, releases, and monitoring                                |
| [Account & users](/query-engine/guides/account-and-users/account-and-user-profile.md) | Account settings and user profiles                                |

## Where to go for other content

* New to e6data? Start with [Get Started](/query-engine/get-started/readme.md).
* Driver and API documentation lives in [Developer](/query-engine/developers/readme-2.md).
* Lookup-style material (SQL functions, error codes, limits) is in [Reference](/query-engine/reference/reference.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/guides/guides.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.