Private connectivity for inbound network traffic in Snowflake Open Catalog¶
Your connection to Snowflake Open Catalog can be routed over the public internet or through a private IP address associated with the cloud platform that hosts your Open Catalog account. By using your cloud platform’s private connectivity solution to create private endpoints, you can harden your security posture so that inbound network traffic uses private connectivity.
When your query engine connects to your Snowflake Open Catalog account, inbound network traffic is generated for your account.
Note
For Snowflake to query Open Catalog–managed tables through private connectivity, Snowflake and Open Catalog must both be located in the same deployment.
Private connectivity for inbound network traffic is supported for the following cloud platforms:
Billing¶
Snowflake calculates costs for inbound private connectivity based on endpoint usage. For details on pricing for inbound private connectivity, see the Snowflake Service Consumption Table.