Google Cloud
Networking
intermediate
Private Service Access — Google Cloud Architecture Template
A consumer VPC reaching an internal-only Cloud Run service and private-IP Cloud SQL through an internal load balancer and private DNS.
Why this architecture works
- Internal load balancing keeps service traffic entirely on Google's private network.
- Cloud SQL over private IP removes the public database endpoint attack surface completely.
- Private DNS zones make internal endpoints addressable by name without public records.
- IAM invoker roles on the Cloud Run service add identity checks on top of network privacy.
What's inside (8 resources)
Consumer VPC
gcp-vpc
Private DNS Zone
gcp-cloud-dns
Internal LB
gcp-cloud-load-balancing
Cloud NAT
gcp-cloud-nat
Private Service
gcp-cloud-run
Private IP Cloud SQL
gcp-cloud-sql
Invoker IAM
gcp-iam
Cloud Monitoring
gcp-monitoring
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform or Pulumi in one click.
- Review the plan diff and security scan, then deploy with human approval.