Skip to main content
This guide describes how to configure private network connections between StreamNative Cloud and Snowflake Horizon Catalog. Private connectivity ensures that traffic between your StreamNative BYOC cluster and Snowflake Horizon Catalog does not traverse the public internet. Snowflake Horizon Catalog uses the same Snowflake private connectivity infrastructure as Snowflake Open Catalog. The setup process is identical across both catalog types. See also Private Networking for Snowflake Open Catalog. The following diagram shows the network path between your StreamNative BYOC cluster and Snowflake Horizon Catalog over private connectivity.

​
Prerequisites

  • A StreamNative BYOC cluster deployed on AWS, GCP, or Azure.
  • A Snowflake account with Horizon Catalog enabled, in the same cloud provider and region as your StreamNative BYOC cluster.
  • Storage private connectivity configured (if applicable). See Private Networking for Catalog Integration for storage connectivity details.

​
Configure private connectivity

Configure private connectivity to Snowflake Horizon 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 Snowflake Horizon Catalog.Follow the Snowflake documentation to configure PrivateLink: Snowflake PrivateLink on AWS.

​
Update the catalog URI

After enabling private connectivity, update the catalog URI in StreamNative Cloud to use the PrivateLink hostname. The catalog URI is configured during catalog registration and can be updated through Manage Catalogs. Change the URI from the public format:
to the PrivateLink format:
The exact private endpoint hostname may vary by cloud provider. Refer to the Snowflake PrivateLink documentation for your cloud provider to determine the correct hostname.