> 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/deployment/aws-serverless/create-cluster.md).

# Create cluster

Create and configure a cluster to run queries in a Serverless e6data workspace on AWS.

A **cluster** is the compute that runs your queries. After connecting a catalog, create a cluster to start querying.

## Create a cluster

1. In the Compute Plane, open the **Clusters** section and select **Create Cluster**.
2. Enter a **Cluster Name** (required). Naming rules:
   * Must start with a letter and end with a letter or digit.
   * 3–30 characters: letters (upper or lower case), numbers, and hyphens (for example, `sales-analytics-01`). Case-sensitive.
3. Select a **Version** (required) - the Cluster Runtime (CRT) version.
4. Select a **Cluster Size** (required) - the compute size.

## Cluster configuration

| Setting                  | What it does                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------- |
| Autoscaling              | Dynamically adjusts cluster size to the workload. Requires a **Maximum Executors (Scale Up To)** value. |
| Window-based scaling     | Available when autoscaling is on. Requires a **Window Duration** in minutes.                            |
| QPS (queries per second) | The expected query load. e6data uses it to determine planner count.                                     |
| Caching                  | Stores query results for faster repeated execution.                                                     |

## Advanced settings

Select **Advanced Settings** to expand these options:

| Setting            | Default              | Notes                                                                                                   |
| ------------------ | -------------------- | ------------------------------------------------------------------------------------------------------- |
| Auto Suspension    | Enabled (30 minutes) | Suspends the cluster after the set minutes of inactivity.                                               |
| Auto Resume        | Enabled              | Resumes the cluster automatically when a query is run.                                                  |
| Result Set Caching | Disabled             | When enabled, set a cache retention time in minutes (default 60).                                       |
| Transpiler         | None                 | Converts queries to a selected SQL dialect for compatibility: Snowflake, Trino, or Databricks.          |
| Query Timeout      | Disabled             | When enabled, set a timeout in seconds (for example, `3600` for one hour) to stop long-running queries. |

For deeper guidance on these options, see [Cluster sizing and scaling](/query-engine/guides/clusters/cluster-sizing-and-scaling.md) and [Suspend and resume](/query-engine/guides/clusters/suspend-and-resume.md).

## See also

* [Run your first query](/query-engine/guides/deployment/aws-serverless/run-first-query.md) - confirm the cluster works.
* [Create and manage clusters](/query-engine/guides/clusters/create-and-manage-clusters.md) - full cluster reference.


---

# 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/deployment/aws-serverless/create-cluster.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.