Google Cloud Platform (GCP) Private Service Connect

Google Private Service Connect ↗ provides private connectivity to Foundry by ensuring traffic occurs from the customer Virtual Private Cloud (VPC) to the Foundry VPC using the Google backbone and avoids the public Internet. Google Private Service Connect supports connections between different virtual private network (VPC) regions. Google Private Service Connect is a Google service.

Ingress to Foundry for Google Cloud Platform (GCP) Private Service Connect

Traffic can occur from the customer Virtual Private Cloud (VPC) to the Foundry VPC using the Google backbone network. Private Link traffic and open Internet traffic to Foundry are supported at the same time by configuring additional IP whitelists using the Ingress Configuration in Control Panel.

Set up GCP Private Service Connect ingress

  1. Send your Google Cloud project ID ↗ to Palantir Support.
  2. Palantir Support will send back the service attachment ID of your Foundry instance, in the form projects/<SERVICE_PROJECT>/regions/<REGION>/serviceAttachments/<SERVICE_NAME>.
  3. Create a Private Service Connect endpoint ↗ in your VPC that targets the Foundry service attachment.
  4. Send the endpoint ID ↗ (the selfLinkWithId value) to Palantir Support.
  5. Foundry accepts the endpoint connection request. If Foundry did not auto-approve the request, contact Palantir Support to approve it.
  6. Configure DNS in your VPC so that the Foundry domain resolves to the internal IP address of the endpoint, for example, with an A record in a Cloud DNS private zone ↗.
  7. If the Foundry domain is owned by you (that is, not a Palantir-owned domain such as *.palantirfoundry.com), follow the additional steps in the documentation on customer-owned domain private links.

Egress from Foundry for GCP Private Service Connect

Traffic can also occur from the Foundry Virtual Private Cloud (VPC) to the customer VPC using the Google global private network.

If your Foundry instance is hosted on GCP, a Private Service Connect endpoint is not needed for Google APIs and services such as BigQuery, Google Cloud Storage, Google Pub/Sub, and other *.googleapis.com APIs. Traffic to these services already remains within Google's network ↗. These connections may still require additional egress configuration.

Set up GCP Private Service Connect egress

  1. Request the Foundry GCP project ID from Palantir Support.
  2. Publish your service ↗ with a service attachment, and add the Foundry GCP project ID to its consumer accept list ↗.
  3. Send the following details to Palantir Support.
    • Service attachment ID: In the form projects/<SERVICE_PROJECT>/regions/<REGION>/serviceAttachments/<SERVICE_NAME>.
    • Custom DNS domains (conditional): Any custom domains your service uses, such as those used by Snowflake or Databricks on GCP.
  4. Palantir creates a Private Service Connect endpoint that targets your service attachment and sends you the endpoint ID.
  5. In the Google Cloud console, verify that the Foundry endpoint is listed as Accepted on your service attachment, and accept the endpoint if it is pending.