Databricks clouds and regions

Databricks workspaces can be hosted on Amazon AWS, Microsoft Azure, and Google Cloud Platform. You can use Databricks on any of these hosting platforms to access data wherever you keep it, regardless of cloud.

This article lists:

  • The regions supported by Databricks on AWS.

  • Features available in each region, where there is regional differentiation in feature availability.

  • IP addresses and domains for Databricks services and assets.

    You may need this information if you create your Databricks workspaces in your own VPC, a feature known as customer-managed VPC, or if you use AWS PrivateLink within your Databricks network environment.

Supported regions list

This table lists the AWS regions supported by Databricks. There are some features that are available only in a subset of regions. The table indicates whether or not a region supports each of these features. If a feature is supported in all regions, it is not included in the table.

Features that are excluded from at least one region include:

Note

Until recently, this table listed region support for Unity Catalog and the E2 platform architecture. Now that these features are supported in all listed regions, the table no longer mentions them.

Region

Location

CMK

PrivateLink

Serverless SQL warehouses

Model Serving

Vector Search

IRAP

Predictive optimization

Firewall support for serverless

ap-northeast-1

Asia Pacific (Tokyo)

X

X

X

ap-northeast-2

Asia Pacific (Seoul)

X

X

ap-south-1

Asia Pacific (Mumbai)

X

X

X

ap-southeast-1

Asia Pacific (Singapore)

X

X

X

X

ap-southeast-2

Asia Pacific (Sydney)

X

X

X (compliance security profile supported)

X

X

X

X

ca-central-1

Canada (Central)

X

X

X

eu-central-1

EU (Frankfurt)

X

X

X

X

X

eu-west-1

EU (Ireland)

X

X

X

X

X

X

eu-west-2

EU (London)

X

X

eu-west-3

EU (Paris)

X

X

X

sa-east-1

South America (Sao Paulo)

X

X

X

us-east-1

US East (Northern Virginia)

X

X

X (compliance security profile supported)

X

X

X

X

us-east-2

US East (Ohio)

X

X

X

X

X

X

us-west-1

US West (Northern California)

us-west-2

US West (Oregon)

X

X

X

X

X

X

X

IP addresses and domains

You may need the following information if:

Webapp addresses

This table lists the address and port of the Databricks web application for each supported region.

VPC region

Address

Port

ap-northeast-1

tokyo.cloud.databricks.com

443

ap-northeast-2

seoul.cloud.databricks.com

443

ap-south-1

mumbai.cloud.databricks.com

443

ap-southeast-1

singapore.cloud.databricks.com

443

ap-southeast-2

sydney.cloud.databricks.com

443

ca-central-1

canada.cloud.databricks.com

443

eu-central-1

frankfurt.cloud.databricks.com

443

eu-west-1

ireland.cloud.databricks.com

443

eu-west-2

london.cloud.databricks.com

443

eu-west-3

paris.cloud.databricks.com

443

sa-east-1

saopaulo.cloud.databricks.com

443

us-east-1

nvirginia.cloud.databricks.com

443

us-east-2

ohio.cloud.databricks.com

443

us-west-1

oregon.cloud.databricks.com

443

us-west-2

oregon.cloud.databricks.com

443

SCC relay addresses

This table lists the address and port used by the secure cluster connectivity (SCC) relay for each supported region.

See Secure cluster connectivity.

VPC region

Address

Port

ap-northeast-1

tunnel.ap-northeast-1.cloud.databricks.com

443

ap-northeast-2

tunnel.ap-northeast-2.cloud.databricks.com

443

ap-south-1

tunnel.ap-south-1.cloud.databricks.com

443

ap-southeast-1

tunnel.ap-southeast-1.cloud.databricks.com

443

ap-southeast-2

tunnel.ap-southeast-2.cloud.databricks.com

443

ca-central-1

tunnel.ca-central-1.cloud.databricks.com

443

eu-central-1

tunnel.eu-central-1.cloud.databricks.com

443

eu-west-1

tunnel.eu-west-1.cloud.databricks.com

443

eu-west-2

tunnel.eu-west-2.cloud.databricks.com

443

eu-west-3

tunnel.eu-west-3.cloud.databricks.com

443

sa-east-1

tunnel.sa-east-1.cloud.databricks.com

443

us-east-1

tunnel.us-east-1.cloud.databricks.com

443

us-east-2

tunnel.us-east-2.cloud.databricks.com

443

us-west-1

tunnel.cloud.databricks.com

443

us-west-2

tunnel.cloud.databricks.com

443

S3 addresses

To add the global S3 bucket service to a route or allow list, use the following address and port, regardless of region: s3.amazonaws.com:443

For regional S3 buckets, AWS provides an address and port for a regional endpoint (s3.<region-name>.amazonaws.com:443), Databricks recommends that you use a VPC endpoint instead. See (Recommended) Configure regional endpoints.

STS addresses

To add the global STS (AWS Security Token Service) to a route or allow list, use the following address and port, regardless of region: sts.amazonaws.com:443

For regional STS, AWS provides an address and port for a regional endpoint (sts.<region-name>.amazonaws.com:443), but Databricks recommends that you use a VPC endpoint instead. See (Recommended) Configure regional endpoints.

Kinesis addresses

For the Kinesis service, AWS provides addresses and ports for regional endpoints as shown in the table below. However, Databricks recommends that you use a VPC endpoint instead. See (Recommended) Configure regional endpoints.

VPC region

Address

Port

us-west-1

kinesis-fips.us-west-2.amazonaws.com

443

All other regions

kinesis.<region-name>.amazonaws.com

443

RDS addresses for legacy Hive metastore

To add the Amazon RDS services used by Databricks to a route or allow list, use the following addresses. These are necessary only if you use the default workspace-level legacy Hive metastore for your workspaces. This does not apply to Unity Catalog metastores.

VPC region

Address

Port

ap-northeast-1

mddx5a4bpbpm05.cfrfsun7mryq.ap-northeast-1.rds.amazonaws.com

3306

ap-northeast-2

md1915a81ruxky5.cfomhrbro6gt.ap-northeast-2.rds.amazonaws.com

3306

ap-south-1

mdjanpojt83v6j.c5jml0fhgver.ap-south-1.rds.amazonaws.com

3306

ap-southeast-1

md1n4trqmokgnhr.csnrqwqko4ho.ap-southeast-1.rds.amazonaws.com

3306

ap-southeast-2

mdnrak3rme5y1c.c5f38tyb1fdu.ap-southeast-2.rds.amazonaws.com

3306

ca-central-1

md1w81rjeh9i4n5.co1tih5pqdrl.ca-central-1.rds.amazonaws.com

3306

eu-central-1

mdv2llxgl8lou0.ceptxxgorjrc.eu-central-1.rds.amazonaws.com

3306

eu-west-1

md15cf9e1wmjgny.cxg30ia2wqgj.eu-west-1.rds.amazonaws.com

3306

eu-west-2

mdio2468d9025m.c6fvhwk6cqca.eu-west-2.rds.amazonaws.com

3306

eu-west-3

metastorerds-dbconsolidationmetastore-asda4em2u6eg.c2ybp3dss6ua.eu-west-3.rds.amazonaws.com

3306

sa-east-1

metastorerds-dbconsolidationmetastore-fqekf3pck8yw.cog1aduyg4im.sa-east-1.rds.amazonaws.com

3306

us-east-1

mdb7sywh50xhpr.chkweekm4xjq.us-east-1.rds.amazonaws.com

3306

us-east-2

md7wf1g369xf22.cluz8hwxjhb6.us-east-2.rds.amazonaws.com

3306

us-west-1

mdzsbtnvk0rnce.c13weuwubexq.us-west-1.rds.amazonaws.com

3306

us-west-2

mdpartyyphlhsp.caj77bnxuhme.us-west-2.rds.amazonaws.com

3306

Control plane infrastructure addresses

This table lists the address and port used by standby infrastructure to improve the stability of Databricks services.

VPC region

Address

Port

ap-northeast-1

35.72.28.0/28

443

ap-northeast-2

3.38.156.176/28

443

ap-south-1

65.0.37.64/28

443

ap-southeast-1

13.214.1.96/28

443

ap-southeast-2

3.26.4.0/28

443

ca-central-1

3.96.84.208/28

443

eu-west-1

3.250.244.112/28

443

eu-west-2

18.134.65.240/28

443

eu-west-3

13.39.141.128/28

443

eu-central-1

18.159.44.32/28

443

sa-east-1

15.229.120.16/28

443

us-east-1

3.237.73.224/28

443

us-east-2

3.128.237.208/28

443

us-west-1 and us-west-2

44.234.192.32/28

443

Control plane and storage bucket addresses

This table includes information required to configure S3 bucket policies and VPC endpoint policies to restrict access to your workspace’s S3 buckets. For more information, see (Optional) Restrict access to S3 buckets.

Region

Control plane NAT IP

VPC ID

Artifact storage bucket

Log storage bucket

System tables bucket

Shared datasets bucket

ap-northeast-1

18.177.16.95

vpc-082c211a3fdc5876e, vpc-0a9dd2f9a99283178

databricks-prod-artifacts-ap-northeast-1

databricks-prod-storage-tokyo

system-tables-prod-ap-northeast-1-uc-metastore-bucket

databricks-datasets-tokyo

ap-northeast-2

54.180.50.119

vpc-04e703ba94a49a3ac, vpc-097fd29f3acba52e8

databricks-prod-artifacts-ap-northeast-2

databricks-prod-storage-seoul

system-tables-prod-ap-northeast-2-uc-metastore-bucket

databricks-datasets-seoul

ap-south-1

13.232.248.161

vpc-042818d612f90f994, vpc-0a0c6fbd8a2890714

databricks-prod-artifacts-ap-south-1

databricks-prod-storage-mumbai

system-tables-prod-ap-south-1-uc-metastore-bucket

databricks-datasets-mumbai

ap-southeast-1

13.213.212.4

vpc-01dcc0ded03337911, vpc-0e0baa0188c149eae

databricks-prod-artifacts-ap-southeast-1

databricks-prod-storage-singapore

system-tables-prod-ap-southeast-1-uc-metastore-bucket

databricks-datasets-singapore

ap-southeast-2

13.237.96.217

vpc-0c2c00de7182adc20, vpc-0a5b21c86d3fc89fa

databricks-prod-artifacts-ap-southeast-2

databricks-prod-storage-sydney

system-tables-prod-ap-southeast-2-uc-metastore-bucket

databricks-datasets-sydney

ca-central-1

35.183.59.105

vpc-0a2b384708459134f, vpc-09e67f3a27be71c9c

databricks-prod-artifacts-ca-central-1

databricks-prod-storage-montreal

system-tables-prod-ca-central-1-uc-metastore-bucket

databricks-datasets-montreal

eu-central-1

18.159.32.64

vpc-0fac49d340642f67b, vpc-0b6768aacb36c9425

databricks-prod-artifacts-eu-central-1

databricks-prod-storage-frankfurt

system-tables-prod-eu-central-1-uc-metastore-bucket

databricks-datasets-frankfurt

eu-west-1

46.137.47.49

vpc-0e362545addfa9470, vpc-0004e2691850f29b3

databricks-prod-artifacts-eu-west-1

databricks-prod-storage-ireland

system-tables-prod-eu-west-1-uc-metastore-bucket

databricks-datasets-ireland

eu-west-2

3.10.112.150

vpc-07eb6b6a2cb9e77eb, vpc-0f0a9d76e15ca7eff

databricks-prod-artifacts-eu-west-2

databricks-prod-storage-london

system-tables-prod-eu-west-2-uc-metastore-bucket

databricks-datasets-london

eu-west-3

15.236.174.74

vpc-0b6f443f7cefdcda2, vpc-01ed1436ea79be8f4

databricks-prod-artifacts-eu-west-3

databricks-prod-storage-paris

system-tables-prod-eu-west-3-uc-metastore-bucket

databricks-datasets-paris

sa-east-1

177.71.254.47

vpc-0b13bcae0aa721cbc, vpc-0717a4601f05c79d9

databricks-prod-artifacts-sa-east-1

databricks-prod-storage-saopaulo

system-tables-prod-sa-east-1-uc-metastore-bucket

databricks-datasets-saopaulo

us-east-1

54.156.226.103

vpc-0e8e0ec90d0f40c06, vpc-08fd12c62a6e0b1df

databricks-prod-artifacts-us-east-1

databricks-prod-storage-virginia

system-tables-prod-us-east-1-uc-metastore-bucket

databricks-datasets-virginia

us-east-2

18.221.200.169

vpc-0865fc77cf45f52b7, vpc-0ea50fe31af7760e4

databricks-prod-artifacts-us-east-2

databricks-prod-storage-ohio

system-tables-prod-us-east-2-uc-metastore-bucket

databricks-datasets-ohio

us-west-1

52.27.216.188

vpc-dc8086b9, vpc-0c51983cc62e5ce0b

databricks-prod-artifacts-us-west-2

databricks-prod-storage-oregon

system-tables-prod-us-west-1-uc-metastore-bucket

databricks-datasets-oregon

us-west-2

52.27.216.188

vpc-dc8086b9, vpc-0c51983cc62e5ce0b

databricks-prod-artifacts-us-west-2 and databricks-update-oregon

databricks-prod-storage-oregon

system-tables-prod-us-west-2-uc-metastore-bucket

databricks-datasets-oregon