Secure tunnel ingress is in the beta phase of development and may not be available on your enrollment. Functionality may change during active development. Contact Palantir Support to request access.
Secure tunnels can carry connections in both directions. Besides routing egress traffic into your network, a secure tunnel cluster can accept TCP connections and UDP traffic from systems in your network. The cluster forwards this traffic to a generic listener in the platform. Systems in your network connect to an initiator as if it were the destination service. The initiator carries the traffic over outbound TLS connections to the platform, so no inbound firewall rules are required between your network and the platform.
This page explains how secure tunnel ingress works, how to restrict which systems can connect to an initiator, and how to troubleshoot connections. To create a generic listener and request an inbound connection policy, review Generic listeners.
Secure tunnel ingress is established by the following components:
| Component | Location | Role |
|---|---|---|
| Client | Your network | The system that opens TCP connections or sends UDP traffic to the initiator. |
| Initiator | Your network | Listens on the gateway port of each approved inbound connection policy, and forwards accepted traffic to the platform over outbound TLS connections. |
| Inbound connection policy | Palantir platform | Authorizes a single generic listener to receive traffic of one transport protocol through one secure tunnel cluster. |
| Generic listener | Palantir platform | Receives the tunneled traffic and delivers it to its backing compute module. |
Traffic follows this path:
<initiator-ip>:<gateway-port>, where <initiator-ip> is the IP address of the initiator and <gateway-port> is the policy's gateway port. For Data Connection agent deployments, a client on the same host as the agent can also connect to localhost:<gateway-port>. Review Connect a client for the address to use in each deployment type.The control plane issues each initiator a separate token for every approved policy on its cluster. Tokens are valid for one hour and rotate automatically, so no long-lived credentials are stored in your network.
Once an inbound connection policy is approved and its listener's compute module is deployed, the cluster's initiators begin listening on the gateway port within a few minutes. Approval alone does not open the gateway port: initiators do not listen for a policy until its compute module is deployed. Gateway ports are allocated from the range 15000 to 16000 and are unique for each protocol within a cluster.
Every initiator in a cluster opens the same gateway ports. How clients reach those ports depends on how the initiator is deployed:
Before you configure secure tunnel ingress, ensure the following:
Secure tunnel ingress has the following limitations:
The initiator's ingress allowlist controls which client IP ranges can connect to which gateway ports. The ingress allowlist denies all ingress by default. An empty ingress allowlist blocks all ingress, even if an inbound connection policy is approved.
The ingress allowlist is separate from the egress allowlist. Each entry specifies a client IP range in cidrBlock and a gateway port. Optionally, set endPort to allow an inclusive range from port through endPort.
For example, the following allowlist permits clients in 10.0.0.0/8 to connect to gateway port 15000, and clients in 192.168.10.0/24 to connect to gateway ports 15000 through 15010:
Copied!1 2 3 4 5 6allowListedIngressCidrs: - cidrBlock: '10.0.0.0/8' port: 15000 - cidrBlock: '192.168.10.0/24' port: 15000 endPort: 15010
Palantir recommends that you allow only the client ranges and gateway ports that each listener requires.
When a Data Connection agent deploys an initiator, the ingress allowlist is empty by default. To edit the ingress allowlist, open the managing agent in Data Connection, navigate to Agent settings > Configuration > Advanced > Envoy, and update the initiator's allowListedIngressCidrs entries.
For Apollo-managed deployments, edit the allowListedIngressCidrs entries on the product's configuration page in Apollo.
Once the policy is approved, the compute module is deployed, the initiator is listening, and the ingress allowlist permits the client, configure the client to connect to the following:
If a client cannot connect, check the following:
lsof -i -P -n | grep <gateway-port> on the agent host to check whether the port is open. For Apollo deployments, the port is open inside the initiator pod, not on the Kubernetes node.0.0.0.0 on the upstream port.