> 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-in-vpc/create-cluster.md).

# Create cluster

Create a cluster in your In-VPC workspace to run queries on the EKS compute Karpenter provisions.

A **cluster** is the compute that runs your queries. In an In-VPC deployment, cluster nodes are provisioned by Karpenter on the workspace NodePool you created during deployment, and scale to zero when idle.

## Create a cluster

1. Open the workspace's Compute Plane and go to the **Clusters** section.
2. Select **Create Cluster** and enter a **Cluster Name** (must start with a letter and end with a letter or digit; letters (upper or lower case), numbers, and hyphens, 3–30 characters; case-sensitive).
3. Select a **Version** - the Cluster Runtime (CRT) - and a **Cluster Size**.
4. Configure autoscaling, QPS, and caching as needed, then create the cluster.

The cluster's pods schedule onto the workspace NodePool (tainted with `workspace-name=<workspace>`), and Karpenter launches nodes to match. For the full set of cluster options, see [Create and manage clusters](/query-engine/guides/clusters/create-and-manage-clusters.md) and [Cluster sizing and scaling](/query-engine/guides/clusters/cluster-sizing-and-scaling.md).

## CloudPrem-specific operations

Operating clusters in an In-VPC deployment - inspecting pods, NodePools, and scaling behavior with `kubectl` - is covered in [CloudPrem cluster operations](/query-engine/guides/clusters/cloudprem-cluster-operations.md).

## Next

Continue to [Run your first query](/query-engine/guides/deployment/aws-in-vpc/run-first-query.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/deployment/aws-in-vpc/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.