Databricks Proxy Onboarding
This page explains how to point your tools at the Espresso AI proxy for Databricks.
General
To use our proxy, configure your tools to point to us instead of directly to your Databricks workspace. Only the domain of the hostname changes; everything else in the connection (the HTTP Path, credentials, catalog, schema) stays the same.
Find the Server Hostname of the Databricks workspace you shared with Espresso AI.
Replace the Databricks domain with
databricks.espressocomputing.com, keeping the rest of the hostname as-is:
AWS
<workspace>.cloud.databricks.com
<workspace>.cloud.databricks.espressocomputing.com
Azure
adb-<workspace_id>.<shard>.azuredatabricks.net
adb-<workspace_id>.<shard>.databricks.espressocomputing.com
GCP
<workspace_id>.<shard>.gcp.databricks.com
<workspace_id>.<shard>.gcp.databricks.espressocomputing.com
For example, dbc-a1b2c3d4-e5f6.cloud.databricks.com becomes dbc-a1b2c3d4-e5f6.cloud.databricks.espressocomputing.com, and adb-1234567890123456.7.azuredatabricks.net becomes adb-1234567890123456.7.databricks.espressocomputing.com.
Leave the HTTP Path unchanged (e.g.
/sql/1.0/warehouses/<warehouse_id>). The proxy uses it to identify the warehouse your tool was configured for.
What the proxy covers
The proxy works with any client that connects to a SQL warehouse over the standard Databricks driver protocol: the JDBC and ODBC drivers, the Databricks SQL connectors for Python, Go and Node.js, and the BI and data tools built on them (Power BI, Tableau, Looker, dbt, Fivetran, Hex, Airflow, and so on). For the Databricks web app itself, use the Chrome extension.
Tool-specific guides
Scheduler Warehouse access
Last updated