Stay organized with collections
Save and categorize content based on your preferences.
This page lists the services supported with producer Virtual Private Cloud spokes.
To use a producer VPC spoke, the service must be consumed by
using private services access. That is, the
name of the peering connection between your VPC network and the
producer VPC network must be servicenetworking-googleapis-com.
For detailed information about producer Virtual Private Cloud (VPC) spokes in
Network Connectivity Center, see Producer VPC spokes.
The following Google services consumed through private services access can be
used with producer VPC spokes.
You can check whether a service producer exports only subnet routes by
listing peering routes and
ensuring that the associated peering connection only has routes of type
Peering subnet.
Producer VPC spokes don't support third-party services.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Supported services for producer VPC spokes\n\nThis page lists the services supported with producer Virtual Private Cloud spokes.\n\nTo use a producer VPC spoke, the service must be consumed by\nusing [private services access](/vpc/docs/private-services-access). That is, the\nname of the peering connection between your VPC network and the\nproducer VPC network must be `servicenetworking-googleapis-com`.\n\nFor detailed information about producer Virtual Private Cloud (VPC) spokes in\nNetwork Connectivity Center, see [Producer VPC spokes](/network-connectivity/docs/network-connectivity-center/concepts/producer-vpc-spokes-overview).\n\nThe following Google services consumed through private services access can be\nused with producer VPC spokes.\n\n- [AlloyDB for PostgreSQL](/alloydb/docs/configure-connectivity)\n- [Apigee](/apigee/docs/api-platform/get-started/configure-service-networking)\n- [Cloud Build](/build/docs/private-pools/private-pools-overview)\n- [Cloud SQL](/sql/docs/mysql/private-ip)\n- [Looker (Google Cloud core)](/looker/docs/looker-core-create-private-ip)\n- [Google Cloud Managed Lustre](/managed-lustre/docs/overview)\n- [Memorystore for Memcached](/memorystore/docs/memcached/establishing-connection)\n- [Memorystore for Redis](/memorystore/docs/redis/establishing-connection)\n- [Vertex AI](/vertex-ai/docs/general/vpc-peering)\n- [Parallelstore](/parallelstore/docs/overview)\n\nYou can check whether a service producer exports only subnet routes by\n[listing peering routes](/vpc/docs/using-vpc-peering#list-peer-routes) and\nensuring that the associated peering connection only has routes of type\n**Peering subnet**.\n\nProducer VPC spokes don't support third-party services.\n\nWhat's next\n-----------\n\n- [Create a producer VPC spoke](/network-connectivity/docs/network-connectivity-center/how-to/create-producer-vpc-spoke)\n- [Troubleshoot Network Connectivity Center](/network-connectivity/docs/network-connectivity-center/support/troubleshooting)\n- [Get details about API and `gcloud` commands](/network-connectivity/docs/network-connectivity-center/apis)"]]
