Features with limited regional availability

This article lists features where there is regional differentiation in feature availability.

Features that are excluded from at least one region include:

Security

Serverless

AI and machine learning

Model serving

Note

Some features are not included in the tables below. These features, known as Designated Services, use Databricks Geos to manage data residency when processing customer content. A Geo is a group of data center regions that Databricks uses to provide predictability and transparency about where your data is processed. See Databricks Designated Services and Databricks Geos: Data residency.

The following tables list the AWS regions supported by Databricks. Some features 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.

Security feature availability

Region	Location	CMK	PrivateLink (classic compute plane)	Firewall enablement for serverless compute
`ap-northeast-1`	Asia Pacific (Tokyo)	✓	✓	✓
`ap-northeast-2`	Asia Pacific (Seoul)	✓	✓
`ap-south-1`	Asia Pacific (Mumbai)	✓	✓	✓
`ap-southeast-1`	Asia Pacific (Singapore)	✓	✓	✓
`ap-southeast-2`	Asia Pacific (Sydney)	✓	✓	✓
`ca-central-1`	Canada (Central)	✓	✓
`eu-central-1`	EU (Frankfurt)	✓	✓	✓
`eu-west-1`	EU (Ireland)	✓	✓	✓
`eu-west-2`	EU (London)	✓	✓
`eu-west-3`	EU (Paris)	✓	✓	✓
`sa-east-1`	South America (Sao Paulo)	✓	✓	✓
`us-east-1`	US East (Northern Virginia)	✓	✓	✓
`us-east-2`	US East (Ohio)	✓	✓	✓
`us-gov-west-1`	US Gov West (Pendleton)	✓	✓
`us-west-1`	US West (Northern California)	✓
`us-west-2`	US West (Oregon)	✓	✓	✓

Serverless compute feature availability

Region	Location	Serverless Compute for Notebooks and Workflows	Serverless DLT Pipelines	Serverless SQL Warehouses	Apps
`ap-northeast-1`	Asia Pacific (Tokyo)	✓	✓	✓
`ap-northeast-2`	Asia Pacific (Seoul)	✓	✓	✓
`ap-south-1`	Asia Pacific (Mumbai)	✓	✓	✓
`ap-southeast-1`	Asia Pacific (Singapore)	✓	✓	✓
`ap-southeast-2`	Asia Pacific (Sydney)	✓	✓	✓	✓
`ca-central-1`	Canada (Central)	✓	✓	✓
`eu-central-1`	EU (Frankfurt)	✓	✓	✓
`eu-west-1`	EU (Ireland)	✓	✓	✓	✓
`eu-west-2`	EU (London)	✓	✓	✓
`eu-west-3`	EU (Paris)	✓	✓	✓
`sa-east-1`	South America (Sao Paulo)	✓	✓	✓
`us-east-1`	US East (Northern Virginia)	✓	✓	✓	✓
`us-east-2`	US East (Ohio)	✓	✓	✓	✓
`us-gov-west-1`	US Gov West (Pendleton)
`us-west-1`	US West (Northern California)
`us-west-2`	US West (Oregon)	✓	✓	✓	✓

Compliance security profile compliance standards with serverless compute availability

Region	Location	None	HIPAA	PCI-DSS	FedRAMP Moderate	IRAP
`ap-northeast-1`	Asia Pacific (Tokyo)	✓	✓
`ap-northeast-2`	Asia Pacific (Seoul)	✓	✓
`ap-south-1`	Asia Pacific (Mumbai)	✓	✓
`ap-southeast-1`	Asia Pacific (Singapore)	✓	✓
`ap-southeast-2`	Asia Pacific (Sydney)	✓	✓	✓		✓
`ca-central-1`	Canada (Central)	✓	✓
`eu-central-1`	EU (Frankfurt)	✓	✓
`eu-west-1`	EU (Ireland)	✓	✓
`eu-west-2`	EU (London)	✓	✓
`eu-west-3`	EU (Paris)	✓	✓
`sa-east-1`	South America (Sao Paulo)	✓	✓
`us-east-1`	US East (Northern Virginia)	✓	✓	✓	✓
`us-east-2`	US East (Ohio)	✓	✓
`us-gov-west-1`	US Gov West (Pendleton)
`us-west-1`	US West (Northern California)
`us-west-2`	US West (Oregon)	✓	✓

AI and machine learning feature availability

Region	Location	Vector Search	Predictive Optimization	Mosaic AI Agent Framework & Evaluation	Foundation Model Fine-tuning	AI Functions using Foundation Model APIs
`ap-northeast-1`	Asia Pacific (Tokyo)	✓	✓
`ap-northeast-2`	Asia Pacific (Seoul)		✓
`ap-south-1`	Asia Pacific (Mumbai)	✓	✓
`ap-southeast-1`	Asia Pacific (Singapore)	✓	✓	✓
`ap-southeast-2`	Asia Pacific (Sydney)	✓	✓	✓
`ca-central-1`	Canada (Central)	✓	✓
`eu-central-1`	EU (Frankfurt)	✓	✓	✓		✓
`eu-west-1`	EU (Ireland)	✓	✓	✓		✓
`eu-west-2`	EU (London)
`eu-west-3`	EU (Paris)		✓
`sa-east-1`	South America (Sao Paulo)		✓
`us-east-1`	US East (Northern Virginia)	✓	✓	✓	✓	✓
`us-east-2`	US East (Ohio)	✓	✓	✓		✓
`us-gov-west-1`	US Gov West (Pendleton)
`us-west-1`	US West (Northern California)
`us-west-2`	US West (Oregon)	✓	✓	✓	✓	✓

Model serving feature availability

The following table summarizes region availability for Mosaic AI Model Serving capabilities.

Important

For Foundation Model APIs pay-per-token:

GTE Large (En) and Meta Llama 3.1 70B Instruct models are available in the following pay-per-token EU and US supported regions. See Pay-per-token limits for the additional pay-per-token models supported in US regions.
If your workspace is not in a US or EU region, your workload is routed to the US Databricks Geo. See Databricks Designated Services for which geographies process pay-per-token workloads.

For Foundation Model APIs provisioned throughput, Meta Llama 3.1 and 3.2 models can be downloaded from HuggingFace and served using provisioned throughput endpoints. See Provisioned throughput limits for the model variants and supported regions.

Region	Location	Core Model Serving capability *	Foundation Model APIs (provisioned throughput) **	Foundation Model APIs (pay-per-token)	External models
`ap-northeast-1`	Asia Pacific (Tokyo)	✓	✓	✓†	✓
`ap-northeast-2`	Asia Pacific (Seoul)
`ap-south-1`	Asia Pacific (Mumbai)	✓	✓	✓†	✓
`ap-southeast-1`	Asia Pacific (Singapore)	✓	✓	✓†	✓
`ap-southeast-2`	Asia Pacific (Sydney)	✓	✓	✓†	✓
`ca-central-1`	Canada (Central)	✓	✓		✓
`eu-central-1`	EU (Frankfurt)	✓	✓	✓	✓
`eu-west-1`	EU (Ireland)	✓	✓	✓	✓
`eu-west-2`	EU (London)
`eu-west-3`	EU (Paris)
`sa-east-1`	South America (Sao Paulo)
`us-east-1`	US East (Northern Virginia)	✓	✓	✓	✓
`us-east-2`	US East (Ohio)	✓	✓	✓	✓
`us-gov-west-1`	US Gov West (Pendleton)
`us-west-1`	US West (Northern California)				✓
`us-west-2`	US West (Oregon)	✓	✓	✓	✓

* CPU compute only

** Includes GPU support

† Region supported when cross geography routing is enabled.