KNIME Documentation

Custom VPC and Private Link ​

The Private Connect add-on routes network traffic between your Knime instance and your networks through the cloud provider's internal network. This keeps it off the public internet. Private Connect is available only with a Private environment deployment.

Private Connect supports two use cases:

  • Allow Knime executors to access on-premises data sources over a private network connection.
  • Route traffic between Knime and your end users through a private network.

INFO

Private Connect requires a cloud account with VPN access to your secure networks.

Connectivity is established using AWS PrivateLink or Azure Private Link, giving you a direct connection between Knime's VPC and your VPC without deploying or maintaining a full VPN.

Setup responsibilities ​

Setting up Private Connect requires both you and Knime to create and operate components in each side's own VPC.

For connecting Knime executors to your data sources, you front your data source with a load balancer, create the endpoint service, and accept the connection from Knime. Knime creates the private endpoint and initiates the connection.

For private access to your Knime instance, Knime fronts it with a load balancer and creates the endpoint service. You create the private endpoint, initiate the connection, and provide VPN connectivity for your users.