Skip to main content
A cluster is the compute layer of e6data. It receives SQL queries, plans execution, and distributes work across executor nodes. You size it for your workload; e6data handles auto-scaling, suspend/resume, and zero-downtime upgrades. A cluster connects to one or more catalogs, and every query is routed to the cluster named in your connection string. The cluster name is 3–30 characters - letters (upper or lower case), digits, and hyphens - and is the routing key in every connection. It must start with a letter and end with a letter or digit, is case-sensitive, and cannot be changed after creation. See resource naming conventions for the full rules.
Running e6data in your own VPC? This page covers the Console UI. For the kubectl/CRD/GitOps workflow, see CloudPrem cluster operations.

​
Create a cluster

  1. Open the Console and go to Clusters.
  2. Click Create Cluster.
  3. Fill in the fields:
  1. Click Create. The cluster moves through Creating → Running and is ready for queries.
You choose a release version when creating or updating a cluster; the e6data team manages the release lifecycle (publishing, testing, deprecation), so you always pick from a curated, validated set.

​
Configure a cluster

After creation, tune these from Cluster → Settings: Execution mode (standard vs. native) and result caching as performance levers are covered in Cluster sizing and scaling.

​
Connect to a cluster

Each cluster exposes connection details from Cluster → Connection. The same cluster supports several protocols simultaneously - pick whichever fits your client: For any method you need the endpoint hostname, port (typically 443 for gRPC/HTTP, 5432 for PostgreSQL), authentication (a personal access token, recommended), the catalog name, and the cluster name. Endpoints are tied to the workspace, not the cluster, so suspending or recreating a cluster keeps the endpoint stable. See Connecting to the engine for tool-specific guides and Endpoints and cluster ingress for allowlisting.

​
Manage and upgrade

Edit a cluster’s settings or version from Cluster → Settings. Changing the version triggers a zero-downtime upgrade: the new version is brought up alongside the current one, traffic switches over once it’s healthy, and the old version drains in-flight queries before shutting down - queries are never interrupted. See Zero-downtime upgrades.

​
Cluster states

The full state machine and error codes are in Lifecycle states and error codes.

​
See also

Last modified on October 1, 2026