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](https://docs.cloud.google.com/vpc/docs/private-services-access) or
[VPC Network Peering](https://docs.cloud.google.com/vpc/docs/vpc-peering). That is, the
name of the peering connection between your VPC network and the
producer VPC network must be `servicenetworking-googleapis-com`.

The following Google services consumed through private services access can be
used with producer VPC spokes.

If you're using [Google Cloud NetApp Volumes](https://docs.cloud.google.com/netapp/volumes/docs/get-started/configure-access/networking),
the name of the peering connection must be `sn-netapp-*`.

For detailed information, see the following resources:

- For information about configuring private service access, see [Configure private services access](https://docs.cloud.google.com/netapp/volumes/docs/get-started/configure-access/networking#configure_private_services_access).

- For information about producer Virtual Private Cloud (VPC) spokes in
  Network Connectivity Center (NCC), see [Producer VPC spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/producer-vpc-spokes-overview).

The following Google services consumed through private services access
can be used with producer VPC spokes.

- [AlloyDB for PostgreSQL](https://docs.cloud.google.com/alloydb/docs/configure-connectivity)
- [Apigee](https://docs.cloud.google.com/apigee/docs/api-platform/get-started/configure-service-networking)
- [Cloud Build](https://docs.cloud.google.com/build/docs/private-pools/private-pools-overview)
- [Cloud SQL](https://docs.cloud.google.com/sql/docs/mysql/private-ip)
- [Filestore](https://docs.cloud.google.com/filestore/docs/overview)
- [Google Cloud Managed Lustre](https://docs.cloud.google.com/managed-lustre/docs/overview)
- [Google Cloud NetApp Volumes](https://docs.cloud.google.com/netapp/volumes/docs/plan-and-prepare/connect-additional-networks#connect-additional-networks-with-ncc)
- [Looker (Google Cloud core)](https://docs.cloud.google.com/looker/docs/looker-core-create-private-ip)
- [Memorystore for Memcached](https://docs.cloud.google.com/memorystore/docs/memcached/establishing-connection)
- [Memorystore for Redis](https://docs.cloud.google.com/memorystore/docs/redis/establishing-connection)
- [Vertex AI](https://docs.cloud.google.com/vertex-ai/docs/general/vpc-peering)

You can check whether a service producer exports only subnet routes by
[listing peering routes](https://docs.cloud.google.com/vpc/docs/using-vpc-peering#list-peer-routes) and
ensuring that the associated peering connection only has routes of type
**Peering subnet**.

Producer VPC spokes don't support third-party services.

## What's next

- [Create a producer VPC spoke](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/create-producer-vpc-spoke)
- [Troubleshoot NCC](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/support/troubleshooting)
- [Get details about API and `gcloud` commands](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/apis)