Features with limited regional availability

This article lists features with availability differences by region.

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 support for features that are only available on a subset of AWS regions. The tables indicate whether or not a region supports each of these features. If a feature is supported in all regions, it is not included.

Security features availability

The following table shows supported regions for these security features that have limited availability:

• Customer-managed keys (CMK)
• AWS PrivateLink (classic)
• Firewall enablement for serverless compute

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)	✓	✓	✓
ap-southeast-3	Asia Pacific (Jakarta)	✓	✓	✓
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 standards with serverless and standard compute availability

For a table of supported regions for compliance standards by compute type, see Classic and serverless compute support by region.

Serverless availability

The following table shows supported regions for these serverless features that have limited availability:

• Serverless compute: Notebooks, jobs, pipelines, and SQL warehouses
• Model Training - forecasting
• Databricks Apps
• Serverless workspaces
• Default storage

Region	Location	Serverless compute (notebooks, jobs, pipelines, and SQL warehouses)	Model Training - forecasting	Databricks Apps	Serverless workspaces	Default storage
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)	✓	✓	✓	✓	✓
ap-southeast-3	Asia Pacific (Jakarta)	✓		✓	✓	✓
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 for notebooks, jobs, and Lakeflow Spark Declarative Pipelines is Public Preview in Databricks on AWS GovCloud and Databricks on AWS GovCloud DoD. Serverless compute for sql warehouses is Public Preview in Databricks on AWS GovCloud and Beta in Databricks on AWS GovCloud DoD. See Databricks on AWS GovCloud.

Ingestion availability

The following table shows supported regions for these ingestion features that have limited availability:

• Managed connectors in Lakeflow Connect
• Zerobus Ingest connector overview

Region	Location	Managed connectors in Lakeflow Connect	Zerobus Ingest
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)	✓	✓
ap-southeast-3	Asia Pacific (Jakarta)	✓
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 features availability

The following table shows supported regions for these AI and machine learning features that have limited availability:

• Predictive optimization
• Vector Search
• Foundation Model Fine-tuning
• Databricks Data Quality Monitoring

Region	Location	Vector Search	Predictive Optimization	Foundation Model Fine-tuning	Data Quality Monitoring
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)	✓	✓		✓
ap-southeast-3	Asia Pacific (Jakarta)		✓
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)	✓	✓	✓	✓

⥂ Region supported only when cross geography routing is enabled. Foundation Model API workloads that rely on GPU compute availability, such as workloads that use models from the Meta Llama family, require cross geography routing.

AI agent features availability

The following table shows supported regions for these agent features that have limited availability:

• Agent Framework and Agent Evaluation
• Knowledge Assistant and Supervisor Agent

Region	Location	Agent Framework & Evaluation	Knowledge Assistant	Supervisor Agent
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)	✓	✓⥂	✓⥂
ap-southeast-3	Asia Pacific (Jakarta)
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)	✓	✓	✓

⥂ Region supported only when cross geography routing is enabled. Foundation Model API workloads that rely on GPU compute availability, such as workloads that use models from the Meta Llama family, require cross geography routing.

AI function availability

The following table shows supported regions for these AI functions that have limited availability:

• ai_query (batch inference)
• ai_parse_document v2
• ai_forecast
• ai_extract and ai_classify v2
• Other AI functions (ai_classify, ai_extract, ai_summarize, ai_gen, and others)

Region	Location	ai_query (batch inference)	ai_parse_document v2	ai_forecast	ai_extract and ai_classify v2	Other AI functions
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)	✓	✓⥂	✓	✓	✓
ap-southeast-3	Asia Pacific (Jakarta)			✓
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)	✓	✓	✓	✓	✓

⥂ Region supported only when cross geography routing is enabled.

‡ Asia Geo traffic can be sent for processing within regions in Japan, South Korea or Singapore. If your workspace is in a Japan region, then traffic is processed in that region.

Model serving features availability

The following table shows supported regions for these Model Serving capabilities and features that have limited availability:

• Core Model Serving
• Foundation Model API pay-per-token
• Foundation Model API provisioned throughput
• External models
• AI Gateway (Beta)

important

For Foundation Model APIs pay-per-token:

• Databricks-hosted models are only available in certain regions. For some models, the model provider determines the region availability that Databricks must follow. See Foundation models hosted on Databricks for which models are supported in each region.

• If your workspace is in a Model Serving region, but not in a US or EU region, you might be able to enable cross region data processing. 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 Foundation models hosted on Databricks for supported regions and model variants.

Region	Location	Core Model Serving capability (CPU serving)	Core Model Serving capability (GPU serving)	External models	Foundation Model APIs (provisioned throughput) **	Foundation Model APIs (pay-per-token)	AI Gateway (Beta)
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)	✓	✓	✓	✓	✓⥂	✓
ap-southeast-3	Asia Pacific (Jakarta)
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)	✓	✓	✓	✓	✓	✓

** Includes GPU support

⥂ Region supported only when cross geography routing is enabled. Foundation Model API workloads that rely on GPU compute availability, such as workloads that use models from the Meta Llama family, require cross geography routing.

‡ Asia Geo traffic can be sent for processing within regions in Japan, South Korea or Singapore. If your workspace is in a Japan region, then traffic is processed in that region.