# Databricks

Apono enables you to automate and control access to Databricks by dynamically managing group memberships through just-in-time access flows. This ensures that data analysts, data scientists, and engineers receive only the temporary, task-based access they need to work with sensitive datasets.

With Apono’s Databricks integration, you can streamline access requests, approvals, and lifecycle management for Databricks groups:

* **Enable self-service access requests** by controlling resource access through Databricks group memberships
* **Enforce zero standing privileges** by automatically revoking expired access
* **Discover and manage permissions** across Databricks groups

***

### Prerequisites

<table><thead><tr><th width="211">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Apono connector</strong></td><td><p>On-prem connection serving as a bridge between a Databricks instance and Apono:</p><ul><li><a href="../../aws-environment/apono-connector-for-aws">AWS</a></li><li><a href="../../azure-environment/apono-connector-for-azure">Azure</a></li><li><a href="../../gcp-environment/apono-connector-for-gcp">GCP</a></li><li><a href="../../kubernetes-environment/apono-connector-for-kubernetes">Kubernetes</a><br></li></ul><p>Learn how to update an existing <a href="../../aws-environment/apono-connector-for-aws/updating-a-connector-in-aws">AWS</a>, <a href="../../azure-environment/apono-connector-for-azure/updating-a-connector-in-azure">Azure</a>, <a href="../../gcp-environment/apono-connector-for-gcp/updating-a-connector-in-google-cloud">GCP</a>, or <a href="../../kubernetes-environment/apono-connector-for-kubernetes/updating-a-kubernetes-connector">Kubernetes</a> connector.</p></td></tr><tr><td><strong>Databricks account management URL</strong></td><td>Accounts Management URL<br><strong>Example</strong>: <em>https://aacounts.cloud.databricks.com</em></td></tr><tr><td><strong>Databricks account ID</strong></td><td><p>Unique identifier for the Databricks account<br><br>Follow these steps:</p><ol><li>In your account management console, click your profile icon.</li><li>Copy the <strong>Account ID</strong> under your email.</li></ol></td></tr><tr><td><strong>Service principal</strong></td><td><p>Account for the Apono integration with admin privileges<br><br>Follow these steps:</p><ol><li>In your account management console, click your workspace <strong>> Manage account</strong>. A new page opens.</li><li>From the side navigation, click <strong>User management</strong>. The <strong>User management</strong> page opens.</li><li>On the <strong>Service principals</strong> tab, click <strong>Add service principal</strong>. The <strong>Add service principal</strong> popup window appears.</li><li>Enter the <strong>New service principal display name</strong>.</li><li>Click <strong>Add service principal</strong>. The principal is created and added to the list of principals.</li><li>Click the name of the principal.</li><li>On the <strong>Roles</strong> tab, click the <strong>Account Admin</strong> toggle to ON.</li><li><p>Grant principal access:</p><ol><li>On the <strong>Permissions</strong> tab, click <strong>Grant accesss</strong>. The <strong>Grant access to others</strong> pop-up window appears.</li><li>From the <strong>User, Group or Service Principal</strong> dropdown menu, select the principal.</li><li>From the <strong>Permission</strong> dropdown menu, select <strong>Service Principal: Manager</strong>.</li><li>Click <strong>Save</strong>.</li></ol></li></ol></td></tr><tr><td><strong>Databricks credentials</strong></td><td><p>Client ID and secret used to securely authenticate the service principal<br><br>Follow these steps:</p><ol><li>On the <strong>Credentials &#x26; secrets</strong> tab of the service principal, click <strong>Generate secret</strong>. The <strong>Generate OAuth secret</strong> popup window opens.</li><li>Enter the <strong>Lifetime (days)</strong> duration of the secret.</li><li>Click <strong>Generate</strong>. The <strong>Generate OAuth secret</strong> popup window is replaced by the <strong>Generate secret</strong> popup window.</li><li>Copy the <strong>Secret</strong> and <strong>Client ID</strong>.</li></ol><p><a href="../../connectors-and-secrets/apono-integration-secret">Create your secret</a> based on your secret and client ID key:</p><p><code>"client_id": "&#x3C;DATABRICKS_CLIENT_ID>",</code></p><p><code>"client_secret": "&#x3C;DATABRICKS_SECRET>"</code></p></td></tr></tbody></table>

***

### Integrate Databricks

<figure><img src="https://1094436629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv6MBfUGvblSdAz31yJXm%2Fuploads%2Fgit-blob-7e48ac63c093c204119e5c40ed942faa6a406927%2Fintegrate-databricks%20(1).png?alt=media" alt="" width="375"><figcaption><p>Databricks tile</p></figcaption></figure>

{% hint style="success" %}
You can also use the steps below to integrate with Apono using Terraform.

In step **10**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=databricks) tab, click **Databricks**. The **Connect Integration** page appears.
2. Under **Discovery**, click **Next**. The **Apono connector** section expands.
3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

{% hint style="info" %}
If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](https://docs.apono.io/docs/aws-environment/apono-connector-for-aws), [Azure](https://docs.apono.io/docs/azure-environment/apono-connector-for-azure), [GCP](https://docs.apono.io/docs/gcp-environment/apono-connector-for-gcp), [Kubernetes](https://docs.apono.io/docs/kubernetes-environment/apono-connector-for-kubernetes)).
{% endhint %}

4. Click **Next**. The **Integration Config** section expands.
5. Define the **Integration Config** settings.

   <table><thead><tr><th width="218">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow</td></tr><tr><td><strong>Databricks Accounts URL</strong></td><td><p>Accounts Management URL</p><p><strong>Example</strong>: <em>https://aacounts.cloud.databricks.com</em></p></td></tr><tr><td><strong>Account Id</strong></td><td>Unique identifier for the Databricks account</td></tr></tbody></table>
6. Click **Next**. The **Secret Store** section expands.
7. [Associate the secret or credentials](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret).

{% hint style="info" %}
If you select the **Apono** secret manager, enter your Databricks **Secret** and **Client Id**.
{% endhint %}

8. Click **Next**. The **Get more with Apono** section expands.
9. Define the **Get more with Apono** settings.

   <table><thead><tr><th width="220">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
10. Click **Confirm**.

<details>

<summary>💡Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/databricks#terraform-v2) for more details about the schema definition.

</details>

Now that you have completed this integration, you can [create access flows](https://docs.apono.io/docs/access-flows/access-flows) that manage Databricks group memberships to control access to resources.