Private Google Access for On-Premises Hosts over Cloud Interconnect and Cloud VPN

GCP Study Hub
November 12, 2026

Private Google Access for on-premises hosts lets servers in a data center reach Google APIs over Cloud Interconnect or Cloud VPN instead of the internet. Two pieces of configuration make it work. Cloud Router advertises the Google API VIP range to the data center over BGP, and on-premises DNS sends Google API hostnames to that VIP. Both are needed, because one supplies the route and the other makes clients use it. This is a hybrid design topic on the Professional Cloud Network Engineer exam, and it connects Cloud Router advertisement modes with DNS.

Advertising the VIP range from Cloud Router

The data center needs a route to the VIP range, and it learns that route from Cloud Router. You add a custom route advertisement for the range, such as 199.36.153.4/30 for restricted.googleapis.com, and the on-premises routers learn a path to it over BGP.

Adding the range means switching the Cloud Router to custom advertisement mode. In that mode the router should keep advertising all visible subnets alongside the VIP range, so on-premises clients still reach Compute Engine subnets as well as the APIs.

The VIP range then reaches the data center over BGP like any other Google Cloud prefix, so on-premises routing stays dynamic and no hand-built static route is needed for it.

Configuring on-premises DNS

A route to the VIP only helps if clients send API requests to it. On-premises DNS is configured so that *.googleapis.com is a CNAME to the VIP's name, such as restricted.googleapis.com. Because the record is a wildcard, the API hostnames under googleapis.com resolve to the VIP, and requests travel over the hybrid connection along the advertised route.

What the design provides

Because API calls travel over the hybrid connection to a VIP, traffic that uses Cloud Interconnect stays on the Interconnect connection and keeps that connection's SLA. Public API addresses are a different path. Direct Peering, for example, sends requests to public API addresses and carries no Google SLA. Where an on-premises firewall blocks outbound internet traffic, servers also can't slip around the design by calling public API endpoints, so the VIP is the way they reach Google APIs.

It also helps to remember where the traffic starts. These connections begin on-premises, and VPC-side features built for VM traffic don't change that. Cloud NAT, for instance, only translates traffic that starts inside the VPC network, so it does nothing for connections that start on-premises.

Summary for the exam

For the Professional Cloud Network Engineer exam, private API access from on-premises needs two things. The first is a custom advertisement of the VIP range on Cloud Router, in custom mode with all visible subnets still advertised. The second is an on-premises DNS CNAME that points *.googleapis.com at the VIP. With both in place, API traffic from the data center uses the hybrid connection, and over Cloud Interconnect it keeps that connection's SLA.

Our Professional Cloud Network Engineer practice exams cover Private Google Access for on-premises hosts alongside Cloud Router custom advertisements and the Google API VIPs, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow