What is Private Service Connect?

Private Service Connect (PSC) creates private endpoints in your VPC that provide connectivity to Google APIs, supported Google services, and third-party services without using external IP addresses. Traffic stays on Google's network, improving security and performance.

How does PSC differ from Private Google Access?

Private Google Access allows VMs without external IPs to reach Google APIs over default routes. PSC goes further by creating an explicit endpoint with a private IP in your VPC, providing finer-grained DNS and firewall control. PSC also supports connecting to published third-party services.

Do I need to modify DNS for PSC?

Yes. PSC requires DNS configuration so that API hostnames (e.g., storage.googleapis.com) resolve to your PSC endpoint's private IP instead of the public IP. This typically involves creating private DNS zones with CNAME or A records pointing to the PSC endpoint.

GCP Private Service Connect Checker

NetworkingGCP

Check Private Service Connect requirements and DNS configuration for GCP services.

Search GCP Services

15 services available

Raw JSON

Output will appear here...

About This Tool

The GCP Private Service Connect Checker validates the requirements and DNS configuration needed to consume Google APIs and third-party services over private networking using Private Service Connect. It checks endpoint configuration, DNS resolution, and routing to ensure traffic stays on Google's network rather than traversing the public internet.

When to Use This Tool

•Verifying Private Service Connect endpoint configuration before enabling private access to Google APIs.
•Troubleshooting DNS resolution issues where clients resolve public IPs instead of private endpoints.
•Planning Private Service Connect architecture for accessing services across VPC peering boundaries.
•Documenting network requirements for compliance reviews that mandate private API access.

Frequently Asked Questions

What is Private Service Connect?: Private Service Connect (PSC) creates private endpoints in your VPC that provide connectivity to Google APIs, supported Google services, and third-party services without using external IP addresses. Traffic stays on Google's network, improving security and performance.
How does PSC differ from Private Google Access?: Private Google Access allows VMs without external IPs to reach Google APIs over default routes. PSC goes further by creating an explicit endpoint with a private IP in your VPC, providing finer-grained DNS and firewall control. PSC also supports connecting to published third-party services.
Do I need to modify DNS for PSC?: Yes. PSC requires DNS configuration so that API hostnames (e.g., storage.googleapis.com) resolve to your PSC endpoint's private IP instead of the public IP. This typically involves creating private DNS zones with CNAME or A records pointing to the PSC endpoint.

Related Learning Guides

GCP Networking Deep Dive30 min read
VPC Network Design Patterns28 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.