Direct VPC Egress vs Serverless VPC Access Connectors for Cloud Run

GCP Study Hub
November 13, 2026

Cloud Run services and Cloud Run functions do not run inside a VPC network you create, so they need a way to send traffic into one before they can reach private resources there. Google Cloud offers two: Direct VPC egress, which places serverless instances directly in a subnet, and Serverless VPC Access connectors, which run on connector instances. Until one of the two is in place, these workloads are not in a VPC network at all. That is also why deploying them into a new VPC network and peering it with the network that holds the resources gives them no path. For the Professional Cloud Network Engineer exam, the choice between the two mechanisms is mostly about cost and management, and it is just as useful to recognize workloads that need neither.

Direct VPC egress

Direct VPC egress lets Cloud Run services and Cloud Run functions send traffic straight into a subnet of your existing VPC network. Each instance gets an internal IP address from that subnet, so it can reach resources in the network without a middle layer. There are no connector VMs to pay for, and you are billed only for normal network traffic.

That makes Direct VPC egress Google's recommended and cheapest option, especially when traffic is low and the subnet has free IP addresses. Because each instance takes an address from the subnet, the subnet needs room for them.

Serverless VPC Access connectors

A Serverless VPC Access connector lets services like Cloud Run, Cloud Run functions and App Engine reach a VPC network. The connector runs on instances that are billed all the time, even when traffic is light. Every additional connector brings its own always-on instances and its own management work, so a design with a connector per workload multiplies both.

How the cost models compare

The two mechanisms differ most in what they cost when traffic is quiet. Direct VPC egress has no standing charge beyond normal network traffic, while a connector's instances are billed whether or not traffic flows. That difference is the reason Direct VPC egress is the recommended option for Cloud Run services and Cloud Run functions, as long as the subnet has free addresses for the instances. Connectors still provide VPC access, and they also serve App Engine, but their cost grows with the number of connectors rather than with traffic.

Workloads that never need a connector

Compute Engine VMs and load balancer backends already live in the VPC network, so they never need a Serverless VPC Access connector.

When a Professional Cloud Network Engineer scenario mentions serverless VPC connectivity, the first thing to check is whether the workload is Cloud Run, Cloud Run functions or App Engine. Workloads that already run in the VPC network, such as Compute Engine VMs, have no use for a connector. For Cloud Run and Cloud Run functions, Direct VPC egress is the recommended and lower cost path, and a connector is the alternative that carries an always-on charge.

Our Professional Cloud Network Engineer practice exams cover Direct VPC egress and Serverless VPC Access alongside private services access and Private Google Access, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow