Loading…
Topic
Private Service Connect
1 post about Private Service Connect. Every summary links to the original.
- 1 post
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
How to securely connect internal Cloud Run MCP servers to Gemini Enterprise
Enterprise teams using Gemini Enterprise build custom MCP servers on Cloud Run to connect AI agents to internal APIs, databases, and workflows. Three challenges arise: internal-only ingress blocks public calls, Cloud Run IAM and user OAuth 2.0 must both be verified, and Shared VPCs cannot use wildcard *.run.app DNS zones without breaking other services. The solution uses an Egress Agent Gateway with Private Service Connect to route traffic privately into the VPC, then to Cloud Run via Private Google Access or a global PSC endpoint. FQDN-scoped Private Cloud DNS resolves only the MCP server hostname to a private VIP, avoiding DNS collisions. Gemini Enterprise sends two authorization headers: an OIDC ID token for Cloud Run IAM and the user’s OAuth 2.0 access token for application-level validation. A companion GitHub repository provides a runnable Python MCP server with OAuth 2.0 middleware and step-by-step setup scripts.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.