Skip to main content

Create Workspaces

You'll create Databricks workspaces with dedicated VPC/VNet isolation in ~15–30 min per workspace.

Prereqs: Cloud Tenant ready

Why this matters​

Workspaces are the compute and collaboration boundary in Databricks. Each workspace runs inside a dedicated VPC (AWS), VNet (Azure), or VPC (GCP) that isolates network traffic. Getting the workspace and network layout right at creation time avoids costly re-deployments later.

Mental model​

The industry standard is three workspaces aligned to the software development lifecycle:

  1. Development — where engineers iterate on code and test changes.
  2. Staging — integration testing and user acceptance before production.
  3. Production — stable workloads serving the business.

Each workspace should be isolated at the network level. Isolating environments at the workspace level prevents a failing experiment from touching production data and makes it easier to enforce different access policies per environment.

How it works​

Each cloud provider has two deployment paths:

  • Manual — point-and-click through the account console or cloud portal. Good for a first workspace or proof of concept.
  • Terraform — infrastructure as code for repeatable, version-controlled deployments. Use this for staging and production.

Pick your cloud provider​

AWS​

  • Manual — account console wizard with automated IAM, S3, and VPC resource creation.
  • Terraform — IaC deployment with customer-managed VPC (BYOVPC).

Azure​

  • Manual — Azure portal deployment with managed resource group and VNet.
  • Terraform — IaC deployment with VNet injection.

GCP​

  • Manual — account console wizard with automated service account and GCS configuration.
  • Terraform — IaC deployment with customer-managed VPC (BYOVPC).

Next​