> ## Documentation Index
> Fetch the complete documentation index at: https://docs.streamnative.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Private Networking for Databricks Unity Catalog (Delta Lake)

This guide describes how to configure private network connections between StreamNative Cloud and Databricks Unity Catalog for Delta Lake. Private connectivity ensures that traffic between your StreamNative BYOC cluster and Databricks Unity Catalog does not traverse the public internet.

Databricks Unity Catalog uses the same private connectivity infrastructure for both Delta Lake and Iceberg. If you use Iceberg with Databricks, see [Private Networking for Databricks Unity Catalog (Iceberg)](/cloud/lakehouse/catalogs/private-networking/databricks-iceberg).

The following diagram shows the network path between your StreamNative BYOC cluster and Databricks Unity Catalog over private connectivity.

```mermaid theme={null}
flowchart TB
    subgraph BYOC["StreamNative BYOC VPC"]
        Cluster["BYOC Cluster"]
        Endpoint["Private Endpoint"]
    end

    Databricks["Databricks Unity Catalog<br/>(Delta Lake)"]

    Cluster -->|"catalog API requests"| Endpoint --> Databricks

    classDef byoc fill:#dbeafe,stroke:#2563eb,color:#1e3a8a
    classDef edge fill:#fde68a,stroke:#b45309,color:#451a03
    classDef ext  fill:#ede9fe,stroke:#7c3aed,color:#4c1d95
    class Cluster byoc
    class Endpoint edge
    class Databricks ext
```

## Prerequisites

* A StreamNative BYOC cluster deployed on AWS, GCP, or Azure.
* A Databricks workspace in the same cloud provider and region as your StreamNative BYOC cluster.
* A prepared Databricks Unity Catalog for Delta Lake. See [Prepare Lakehouse Catalogs](/cloud/lakehouse/prepare-lakehouse-catalogs) for the cloud-specific setup guides.
* Storage private connectivity configured (if applicable). See [Private Networking for Catalog Integration](/cloud/lakehouse/catalogs/private-networking/overview) for storage connectivity details.

## Configure private connectivity

Configure private connectivity to Databricks Unity Catalog based on the cloud provider where your StreamNative BYOC cluster is deployed.

<Tabs>
  <Tab title="AWS">
    Use AWS PrivateLink to establish a private connection between your StreamNative Cloud environment and Databricks Unity Catalog.

    Follow the Databricks documentation to configure inbound PrivateLink:
    [Configure Inbound PrivateLink for Databricks](https://docs.databricks.com/en/security/network/front-end/front-end-private-connect.html).
  </Tab>

  <Tab title="GCP">
    Use Google Cloud Private Service Connect to establish a private connection between your StreamNative Cloud environment and Databricks Unity Catalog.

    Follow the Databricks documentation to configure front-end Private Service Connect:
    [Configure Front-end Private Service Connect for Databricks on GCP](https://docs.databricks.com/gcp/en/security/network/front-end/front-end-private-connect.html).
  </Tab>

  <Tab title="Azure">
    Use Azure Private Link to establish a private connection between your StreamNative Cloud environment and Databricks Unity Catalog.

    Follow the Databricks documentation to configure inbound Private Link:
    [Configure Inbound Private Link for Databricks on Azure](https://learn.microsoft.com/en-us/azure/databricks/security/network/front-end/front-end-private-connect).
  </Tab>
</Tabs>

## Update the catalog URI

After enabling private connectivity, you may need to update the catalog URI in StreamNative Cloud. The catalog URI is configured during [catalog registration](/cloud/lakehouse/catalogs/register-catalog) and can be updated through [Manage Catalogs](/cloud/lakehouse/catalogs/manage-catalogs).

<Note>
  If your Databricks workspace is configured with private DNS, the existing workspace URL resolves to the private endpoint automatically and no URI change is needed. Otherwise, update the catalog URI to use the private endpoint hostname.
</Note>