• 18 Nov 2022
  • 1 Minute to read
  • Contributors
  • Dark


  • Dark


In this article we will discuss how to connect a Databricks database to Preset using Databricks Native Connector.

So let's get started!

Allowlist Preset IPs

Preset Cloud currently runs on three regions with the IPs listed below, and those need to be allowlisted so Preset can access your data.

Before starting, please take a moment to allowlist the IPs below based on the region that you're deployed in.

us-west-2 (us1a) us-east-1 (us2a) eu-north-1 (eu5a) ap-northeast-1 (ap1a)

If you are not sure where your Preset workspace is located, you can refer to the URL on your browser when accessing Preset. It should look like this:, where us2a means it is in us-east-1.

Retrieve Databricks Information

Step 1: Get Databricks Token

In Databricks, navigate to User SettingsAccess TokensGenerate New Token.


Step 2: Get Host and URL

Navigate to Clusters and select your cluster.


...then copy and save your host and http path.


Connect using the Native Databricks Connector

Let's start by selecting + Database — have a look at Connecting your Data if you need help wth this step.

...then, in the Connect a database window, scroll down and select the Supported Databases field.

In the drop-down list, select Databricks Native Connector.


Define Display Name and URI

In the Display Name field, enter a database nickname for display in the Preset environment.

In the SQLAlchemy URI field, enter the unique URI based on the following syntax, being careful to enter the relevant token, host, and database name details.


The screen should look as follows:


Provide Additional Parameters

Next, select the Advanced tab and expand the Other panel.

In the Engine Parameters text-entry field, enter the following — be sure to enter the relevant http path retrieved earlier.

{"connect_args": {"http_path": "sql/protocolv1/o/****"}}

The screen should look similar to the following:


Make the Connection

Next, navigate back to the Basic tab and then select Test Connection.

A notification message will appear indicating success or failure. If the test worked, then go ahead and select Connect to finalize the database connection.

Great work!

Was this article helpful?

What's Next