Add a Private Network Route for Snowflake on Amazon Web Services (AWS)

Connect your Snowflake data source and Data 360 tenant with a dedicated network connection by using Private Connect for Data 360. Create a single connection to a specific instance, even if you have multiple Data 360 instances. Before you set up a Snowflake federation connection or data share, create a Private Network Route (PNR).

Required Editions

Available in: All Editions supported by Data 360. See Data 360 edition availability.
User Permissions Needed
To create a Snowflake network route: Data Cloud Architect permission set, Manage External Connections, or Customize Application permission
To administer a Snowflake environment: Snowflake account administrator

Limitations

  • The maximum number of private network routes (PNRs) for a particular Snowflake URL is limited to one per Data 360 functional domain (not per Data 360 org).
  • To connect Data 360 to your Snowflake instance, add the virtual private cloud (VPC) endpoint ID to your organization’s allowlist.

    Alternatively, you can add the internal IP address range 10.0.0.0/8 to your Snowflake network policy's allowlist. Only private networks use this reserved address range. For more information, see Controlling network traffic with network policies in the Snowflake documentation.

  1. From the App Launcher, select Data Cloud.
  2. From Setup, select Data Cloud Setup.
  3. From Data Cloud Setup, expand Admin Tools and select Private Connect.
  4. Select New.

    When the maximum number of licensed private network routes is reached, the New button doesn’t appear. To get more private network routes, speak with your Salesforce account representitve.

  5. On the Add Private Network Route page, select the Snowflake tile.
  6. In the Select a network panel, select AWS and then click Add Private Network Route.
  7. On the Configure Snowflake Private Network Route page, enter a route name. Data 360 autopopulates the Route API name based on the route name.
    You can’t change the route name after you save.
  8. Optionally, in the Description field, enter a description to identify the connection.
  9. In the Account URL field, enter the Snowflake account URL.
  10. In the Virtual Private Cloud endpoint ID field, enter the ID.
    To get the ID, use the SYSTEM$GET_PRIVATELINK_CONFIG function. See the Function and stored procedure reference documentation.
  11. Select Save.

After the network provisioning is complete, create a Snowflake federated connection or data share. Provisioning can take some time. After Data 360 provisions the network route, update the Snowflake network policy. See Update Your Snowflake Network Policy.