Private Connectivity (PrivateLink)
By default, Snowflake is accessed over the public internet. While this traffic is heavily encrypted (TLS 1.2+), highly regulated enterprises (like banking, healthcare, and government) often mandate that their data traffic must never traverse the public internet.
To solve this, Snowflake supports Private Connectivity, allowing your on-premises networks and cloud VPCs to communicate with Snowflake over a completely private, dedicated network path.
Topics Covered
- What is Private Connectivity and Why it Matters
- Cloud Provider Integrations (AWS, Azure, GCP)
- Verifying Connectivity with SnowCD
- Cost and Network Architecture Considerations
What is Private Connectivity?
Private Connectivity uses the underlying cloud provider's private networking features (AWS PrivateLink, Azure Private Link, or GCP Private Service Connect) to create a private endpoint inside your own Virtual Private Cloud (VPC) or VNet.
When a data engineer or an application queries Snowflake via this private endpoint, the traffic stays entirely within the cloud provider's backbone.
Benefits:
- Meets strict compliance and regulatory requirements.
- Protects against public internet routing hijacking and DDoS attacks.
- Often provides lower latency and more consistent network performance.
Cloud Provider Integrations
Snowflake supports private connectivity on all three major clouds. (Note: Private Connectivity requires Snowflake Business Critical Edition or higher).
1. AWS PrivateLink
AWS PrivateLink creates a VPC Endpoint in your AWS environment. Traffic from your AWS resources (like EC2 instances running dbt, or AWS Lambda) routes to this endpoint, which privately connects to the Snowflake AWS VPC.
2. Azure Private Link
Similar to AWS, Azure Private Link creates a private endpoint in your Azure VNet. It assigns a private IP address from your VNet to Snowflake, ensuring traffic from your Azure VMs (e.g., a PowerBI gateway) to Snowflake remains on the Microsoft Azure backbone.
3. GCP Private Service Connect
Google Cloud uses Private Service Connect to create private endpoints in your GCP VPC, routing traffic securely to the Snowflake GCP environment.
Hands-On Demonstration: Setting Up Private Connectivity
Setting up private connectivity requires coordination between a Snowflake ACCOUNTADMIN and a Cloud Network Administrator.
1. Retrieve the Snowflake VPC Details
First, the Snowflake Admin must authorize the customer's Cloud Account to connect.
(To ensure you have the ACCOUNTADMIN role, you can run SELECT CURRENT_USER(); to check your user, and SELECT CURRENT_ROLE(); to check your active role).
USE ROLE ACCOUNTADMIN;
-- Get the system function required to authorize your AWS account (if using AWS)
SELECT SYSTEM$AUTHORIZE_PRIVATELINK(
'123456789012', -- Replace with your AWS Account ID
'443' -- Port
);
-- Retrieve the specific PrivateLink details to give to your Cloud Network Admin
SELECT SYSTEM$GET_PRIVATELINK_CONFIG();
The output of SYSTEM$GET_PRIVATELINK_CONFIG() provides the exact URL you will use (e.g., xy12345.us-east-1.privatelink.snowflakecomputing.com) and the VPCE (VPC Endpoint Service) ID.
2. Cloud Admin Configuration (Conceptual)
The Cloud Network Admin (e.g., Vikram from your Cloud Ops team in Punjab) takes the VPCE ID from the previous step and creates a VPC Endpoint in AWS.
Next, they update the company's internal DNS (like Amazon Route 53) so that xy12345.us-east-1.privatelink.snowflakecomputing.com resolves to the local private IP address of the new VPC Endpoint.
3. Creating a Network Policy
Once the private link is established, you should create a Snowflake Network Policy to enforce its use, ensuring that sensitive applications must connect privately.
USE ROLE SECURITYADMIN;
-- Create a network policy that ONLY allows traffic from your private VPC CIDR block (e.g., 10.0.0.0/16)
CREATE OR REPLACE NETWORK POLICY PRIVATE_ONLY_POLICY
ALLOWED_IP_LIST = ('10.0.0.0/16')
BLOCKED_IP_LIST = ('0.0.0.0/0'); -- Block all public internet traffic
-- Apply the policy to a specific service user
ALTER USER PIPELINE_SVC_USER SET NETWORK_POLICY = PRIVATE_ONLY_POLICY;
Verifying Private Connectivity with SnowCD
SnowCD (Snowflake Connectivity Diagnostic Tool) is a command-line tool you install on a machine inside your VPC. It verifies that your private network path can successfully reach all required Snowflake endpoints (including internal stages for data loading).
- Generate the whitelist JSON from Snowflake:
SELECT SYSTEM$WHITELIST_PRIVATELINK(); - Save the output as
whitelist.jsonon your VPC machine. - Run SnowCD from your terminal:
snowcd whitelist.json
If all checks pass, your Private Connectivity is correctly configured!
Cost and Architecture Considerations
- Snowflake Costs: Snowflake does not charge extra to enable PrivateLink (though it requires the more expensive Business Critical Edition).
- Cloud Provider Costs: AWS, Azure, and GCP do charge for VPC Endpoints and the data processing fees per gigabyte that flows through the private link. For massive ETL workloads, this can add significant cost to your cloud provider bill.
- Cross-Region: PrivateLink typically only works within the same cloud region. If your dbt server is in AWS
ap-south-1(Mumbai) and your Snowflake account is in AWSus-east-1, you cannot easily use PrivateLink without setting up complex cross-region VPC peering.
Summary
- Private Connectivity ensures data traffic never touches the public internet.
- Requires Business Critical Edition.
- Uses AWS PrivateLink, Azure Private Link, or GCP Private Service Connect.
- Use SnowCD to troubleshoot and verify internal routing.
- Can incur significant data transfer costs on your cloud provider bill.