> 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/workspaces/create-and-manage-workspaces.md).

# Create and manage workspaces

Create a workspace in the e6data Console - pick Serverless or In Your VPC, your cloud and region - and update it when a new version is released.

A workspace is the top-level container for catalogs, clusters, and queries. This page covers creating one from the Control Plane and updating it over time.

## Before you start

* Have an e6data account (refer [sign up and login](/query-engine/get-started/identity-access-setup/sign-up-and-login.md)).
* Decide which cloud you'll deploy to (AWS or Azure).
* Decide on a deployment type - Serverless or In Your VPC. See [Deployment models](/query-engine/get-started/deployment-models.md).
* Pick a region - typically where your data resides.

## Create the workspace

From the Control Plane:

1. Open the **Workspaces** menu in the left navigation.
2. Click **Create**.
3. Choose your deployment model:
   * **Serverless** - e6data manages the compute infrastructure.
   * **In Your VPC** - compute runs inside your own Kubernetes cluster.
4. Click **Continue** under your chosen model.
5. Fill in the workspace details:

   | Field              | Description                                                   |
   | ------------------ | ------------------------------------------------------------- |
   | **Cloud Provider** | AWS or Azure                                                  |
   | **Region**         | Where your data resides (for example, `us-east-1`, `East US`) |
   | **Workspace Name** | See [naming rules](#workspace-naming-rules) below             |
6. Click **Create Workspace**.

### Workspace naming rules

* 1–18 characters long.
* Lowercase letters (`a–z`), numbers (`0–9`), and hyphens (`-`) only.
* Must start and end with a letter or number.

See [resource naming conventions](/query-engine/reference/platform-reference/resource-naming-conventions.md) for naming rules across all resources.

| Valid             | Invalid                          |
| ----------------- | -------------------------------- |
| `sales-analytics` | `Sales` (uppercase)              |
| `prod-1`          | `-prod` (starts with hyphen)     |
| `my-workspace-2`  | `my_workspace` (underscore)      |
| `team-a`          | `analytics!` (special character) |

## After creation

Once the workspace shows **Running** in the Workspaces list:

* Click **Open** to enter the Compute Plane.
* Follow the cloud-specific [deployment guide](/query-engine/guides/deployment/aws-serverless.md) to grant storage access (Serverless).
* Once access is granted, [register a catalog](/query-engine/guides/catalogs/register-and-manage-catalogs.md) and [create a cluster](/query-engine/guides/clusters/create-and-manage-clusters.md).

## Workspaces list reference

The list shows the following for each workspace:

| Column             | Description                                       |
| ------------------ | ------------------------------------------------- |
| **Workspace Name** | The name you provided                             |
| **Status**         | `Running`, `Provisioning`, `Disabled`, or `Error` |
| **Type**           | `Serverless` or `In Your VPC`                     |
| **Cloud**          | `AWS` or `Azure`                                  |
| **Region**         | The region you selected                           |

Available row actions: **Open** (launch the Compute Plane), **Enable** / **Disable**, and **Delete**. See [Workspace settings](/query-engine/guides/workspaces/workspace-settings.md).

## See also

* [Workspace settings](/query-engine/guides/workspaces/workspace-settings.md) - enable and disable.
* [Delete workspace](/query-engine/guides/workspaces/delete-workspace.md)
* [Deployment](/query-engine/guides/deployment/aws-serverless.md) - cloud-specific setup guides.


---

# 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/workspaces/create-and-manage-workspaces.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.