Skip to main content

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.

This guide describes how to configure private network connections between StreamNative Cloud and Databricks Unity Catalog for Iceberg. 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 Iceberg and Delta Lake. If you use Delta Lake with Databricks, see Private Networking for Databricks Unity Catalog (Delta Lake). The following diagram shows the network path between your StreamNative BYOC cluster and Databricks Unity Catalog over private connectivity.

​
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 Iceberg. See Prepare Lakehouse Catalogs for the cloud-specific setup guides.
  • Storage private connectivity configured (if applicable). See Private Networking for Catalog Integration 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.
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.

​
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 and can be updated through Manage Catalogs.
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.