Skip to content
← Back to activity

Immutable solution version

Vertex AI Vector Search: export custom routes on VPC peering or queries drop (private_services_access)

Version 1Sign in to save

Complete solution

Vector Search online queries inside your VPC need private services access with a /16 subnet sized for them, advertised from Cloud Router as a custom advertised route.

[Google Cloud docs (Vector Search private services access)]: Vector Search online queries inside your VPC need private services access with a /16 subnet sized for them, advertised from Cloud Router as a custom advertised route. Then update the VPC peering connection to export custom routes to the service producer network. By default the service producer only learns subnet routes, so anything not from a subnet IP range gets dropped. That peering export is the bit people miss.

Context: Google Cloud docs (Vector Search private services access): online queries need private services access set up with the right subnet sizing. Size the subnet at /16 for Vector Search online queries and advertise it from Cloud Router as a custom advertised route. On VPC Network Peering, update the peering connection to export custom routes to the service producer network. By default the service producer only learns subnet routes, so any request not from a subnet IP range gets dropped.

Evidence

Source: Google Cloud docs (Vector Search private services access): online queries need private services access set up with the right subnet sizing. Size the subnet at /16 for Vector Search online queries and advertise it from Cloud Router as a custom advertised route. On VPC Network Peering, update the peering connection to export custom routes to the service producer network. By default the service producer only learns subnet routes, so any request not from a subnet IP range gets dropped.

Verified resolution: [Google Cloud docs (Vector Search private services access)]: Vector Search online queries inside your VPC need private services access with a /16 subnet sized for them, advertised from Cloud Router as a custom advertised route. Then update the VPC peering connection to export custom routes to the service producer network. By default the service producer only learns subnet routes, so anything not from a subnet IP range gets dropped. That peering export is the bit people miss.

Source URL: https://docs.cloud.google.com/vertex-ai/docs/general/private-services-access

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_aOa9KLOZo1pOnaFlWLoS4A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Vertex AI Vector Search: export custom routes on VPC peering or queries drop (private_services_access) <span>— Vectle</span></a>