Set up GCP private connectivity to PostgreSQL
Private connectivity to PostgreSQL on Google Cloud depends on what the database is - Cloud SQL and AlloyDB have Private Service Connect paths under their own connectors; self-managed Postgres uses the self-deployed agent.
On Google Cloud, the private path to PostgreSQL depends on what the database is. Google's equivalent of AWS PrivateLink is Private Service Connect (PSC), and Atlan supports it - but through the GCP-native connectors, not this generic PostgreSQL connector. Find your case below.
Cloud SQL for PostgreSQL
Use the Cloud SQL for PostgreSQL connector, which has its own connectivity guides including Private Service Connect:
AlloyDB for PostgreSQL
Use the AlloyDB for PostgreSQL connector and its connectivity guides:
Self-managed PostgreSQL on GCP (Compute Engine, GKE)
There is no documented private-link path for a self-managed Postgres on GCP today. The supported private option is the self-deployed agent: it runs inside your network, reaches the database locally, and makes only outbound HTTPS calls to your Atlan tenant - no inbound rule, no public endpoint.
If the agent's host needs a web proxy to reach your Atlan tenant, configure the proxy in the agent's compose file - a missing proxy setting is a known cause of "agent not detected" during workflow setup.
Can I use the internet path instead?
Yes - if the database has (or may have) a public endpoint, the standard internet + IP allowlisting guide applies. Note for GCP-hosted Atlan tenants: Atlan publishes static outbound NAT IPs per GCP region - see Atlan Network Details. Confirm with support that they apply to your tenant before relying on them.
Any step failing - see Troubleshooting PostgreSQL connectivity.