Supported products and limitations

For more information about Infrastructure Manager, refer to the product documentation.

To use Workload Manager in a VPC Service Controls perimeter:

• You must use a Cloud Build private worker pool for your deployment environment in Workload Manager. You cannot use the default Cloud Build worker pool.
• The Cloud Build private pool must have public internet calls enabled to download the Terraform configuration.

For more information, see Use a Cloud Build private worker pool in the Workload Manager documentation.

For more information about Workload Manager, refer to the product documentation.

The API for Google Cloud NetApp Volumes can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Google Cloud NetApp Volumes, refer to the product documentation.

Google Cloud Search supports Virtual Private Cloud Security Controls (VPC Service Controls) to enhance the security of your data. VPC Service Controls allows you to define a security perimeter around Google Cloud Platform resources to constrain data and help mitigate data exfiltration risks.

For more information about Google Cloud Search, refer to the product documentation.

The API for Connectivity Tests can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Connectivity Tests, refer to the product documentation.

The Connectivity Tests integration with VPC Service Controls has no known limitations.

VPC Service Controls supports online prediction, but not batch prediction.

For more information about AI Platform Prediction, refer to the product documentation.

The API for AI Platform Training can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about AI Platform Training, refer to the product documentation.

VPC Service Controls perimeters protect the AlloyDB API.

For more information about AlloyDB for PostgreSQL, refer to the product documentation.

• Service perimeters protect only the AlloyDB for PostgreSQL Admin API. They don't protect IP-based data access to underlying databases (such as AlloyDB for PostgreSQL instances). To restrict public IP access on AlloyDB for PostgreSQL instances, use an organization policy constraint.
• Before you configure VPC Service Controls for AlloyDB for PostgreSQL, enable the Service Networking API.
• When you use AlloyDB for PostgreSQL with Shared VPC and VPC Service Controls, the host project and service project must be in the same VPC Service Controls service perimeter.

The API for Vertex AI Workbench can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Vertex AI Workbench, refer to the product documentation.

The API for Vertex AI can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

See Colab Enterprise.

For more information about Vertex AI, refer to the product documentation.

The API for Vertex AI Vision can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Vertex AI Vision, refer to the product documentation.

The API for Vertex AI in Firebase can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Vertex AI in Firebase, refer to the product documentation.

The API for Colab Enterprise can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

Colab Enterprise is a part of Vertex AI. See Vertex AI.

Colab Enterprise uses Dataform for storing notebooks. See Dataform.

For more information about Colab Enterprise, refer to the product documentation.

The API for Apigee and Apigee hybrid can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Apigee and Apigee hybrid, refer to the product documentation.

For more information about Analytics Hub, refer to the product documentation.

The API for Cloud Service Mesh can be protected by VPC Service Controls, and the product can be used normally inside service perimeters.

You can use mesh.googleapis.com to enable the required APIs for Cloud Service Mesh. You don't need to restrict mesh.googleapis.com in your perimeter as it doesn't expose any APIs.

• Learn about configuring VPC Service Controls for Cloud Service Mesh (Managed).
• Learn about adding Cloud Service Mesh services to the service perimeters.

For more information about Cloud Service Mesh, refer to the product documentation.

The Cloud Service Mesh integration with VPC Service Controls has no known limitations.

In addition to protecting the Artifact Registry API, Artifact Registry can be used inside service perimeters with GKE and Compute Engine.

For more information about Artifact Registry, refer to the product documentation.

The API for Assured Workloads can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Assured Workloads, refer to the product documentation.

The Assured Workloads integration with VPC Service Controls has no known limitations.

To fully protect the AutoML API, include all of the following APIs in your perimeter:

• AutoML API (automl.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• BigQuery API (bigquery.googleapis.com)

For more information about AutoML Natural Language, refer to the product documentation.

To fully protect the AutoML API, include all of the following APIs in your perimeter:

• AutoML API (automl.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• BigQuery API (bigquery.googleapis.com)

For more information about AutoML Tables, refer to the product documentation.

To fully protect the AutoML API, include all of the following APIs in your perimeter:

• AutoML API (automl.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• BigQuery API (bigquery.googleapis.com)

For more information about AutoML Translation, refer to the product documentation.

To fully protect the AutoML API, include all of the following APIs in your perimeter:

• AutoML API (automl.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• BigQuery API (bigquery.googleapis.com)

For more information about AutoML Video Intelligence, refer to the product documentation.

To fully protect the AutoML API, include all of the following APIs in your perimeter:

• AutoML API (automl.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• BigQuery API (bigquery.googleapis.com)

For more information about AutoML Vision, refer to the product documentation.

The Bare Metal Solution API can be added to a secure perimeter. However, the VPC Service Controls perimeters do not extend to the Bare Metal Solution environment in the regional extensions.

For more information about Bare Metal Solution, refer to the product documentation.

Connecting VPC Service Controls to your Bare Metal Solution environment doesn't uphold any service control guarantees.

For more information about Bare Metal Solution limitation regarding VPC Service Controls, see Known issues and limitations.

The API for Batch can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Batch, refer to the product documentation.

The API for BigLake Metastore can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about BigLake Metastore, refer to the product documentation.

The BigLake Metastore integration with VPC Service Controls has no known limitations.

When you protect the BigQuery API using a service perimeter, the BigQuery Storage API, BigQuery Reservation API, and BigQuery Connection API are also protected. You do not need to separately add these APIs to your perimeter's list of protected services.

For more information about BigQuery, refer to the product documentation.

The BigQuery Data Policy API can be protected by VPC Service Controls, and the product can be used normally inside service perimeters.

For more information about BigQuery Data Policy API, refer to the product documentation.

The BigQuery Data Policy API integration with VPC Service Controls has no known limitations.

Service perimeter only protects BigQuery Data Transfer Service API. The actual data protection is enforced by BigQuery. It is by design to allow importing data from various external sources outside of Google Cloud, such as Amazon S3, Redshift, Teradata, YouTube, Google Play and Google Ads, into BigQuery datasets. For information about VPC Service Controls requirements to migrate data from Teradata, see VPC Service controls requirements.

For more information about BigQuery Data Transfer Service, refer to the product documentation.

The BigQuery Migration API can be protected by VPC Service Controls, and the product can be used normally inside service perimeters.

For more information about BigQuery Migration API, refer to the product documentation.

The BigQuery Migration API integration with VPC Service Controls has no known limitations.

The bigtable.googleapis.com and bigtableadmin.googleapis.com services are bundled together. When you restrict the bigtable.googleapis.com service in a perimeter, the perimeter restricts the bigtableadmin.googleapis.com service by default. You cannot add the bigtableadmin.googleapis.com service to the list of restricted services in a perimeter because it is bundled with bigtable.googleapis.com.

For more information about Bigtable, refer to the product documentation.

The Bigtable integration with VPC Service Controls has no known limitations.

When using multiple projects with Binary Authorization, each project must be included in the VPC Service Controls perimeter. For more information about this use case, see Multi-project setup.

With Binary Authorization, you may use Artifact Analysis to store attestors and attestations as notes and occurrences, respectively. In this case, you must also include Artifact Analysis in the VPC Service Controls perimeter. See VPC Service Controls guidance for Artifact Analysis for additional details.

For more information about Binary Authorization, refer to the product documentation.

The Binary Authorization integration with VPC Service Controls has no known limitations.

The API for Blockchain Node Engine can be protected by VPC Service Controls and used normally inside service perimeters.

For more information about Blockchain Node Engine, refer to the product documentation.

The API for Certificate Authority Service can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Certificate Authority Service, refer to the product documentation.

To use Config Controller with VPC Service Controls, you must enable the following APIs inside your perimeter:

• Cloud Monitoring API (monitoring.googleapis.com)
• Container Registry API (containerregistry.googleapis.com)
• Google Cloud Observability API (logging.googleapis.com)
• Security Token Service API (sts.googleapis.com)
• Cloud Storage API (storage.googleapis.com)

If you provision resources with Config Controller, you must enable the API for those resources in your service perimeter. For example, if you want to add an IAM service account, you must add the IAM API (iam.googleapis.com).

For more information about Config Controller, refer to the product documentation.

The Config Controller integration with VPC Service Controls has no known limitations.

For more information about Data Catalog, refer to the product documentation.

The Data Catalog integration with VPC Service Controls has no known limitations.

Cloud Data Fusion requires some special steps to protect using VPC Service Controls.

For more information about Cloud Data Fusion, refer to the product documentation.

The API for Data Lineage API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Data Lineage API, refer to the product documentation.

The Data Lineage API integration with VPC Service Controls has no known limitations.

VPC Service Controls support for Compute Engine offers the following security benefits:

• Restricts access to sensitive API operations
• Restricts persistent disk snapshots and custom images to a perimeter
• Restricts access to instance metadata

VPC Service Controls support for Compute Engine also enables you to utilize Virtual Private Cloud networks and Google Kubernetes Engine private clusters inside service perimeters.

For more information about Compute Engine, refer to the product documentation.

To use Conversational Insights with VPC Service Controls you must have the following additional APIs inside your perimeter, depending on your integration.

• To load data into Conversational Insights, add the Cloud Storage API to your service perimeter.

• To use export, add the BigQuery API to your service perimeter.

• To integrate multiple CCAI products, add the Vertex AI API to your service perimeter.

For more information about Conversational Insights, refer to the product documentation.

The Conversational Insights integration with VPC Service Controls has no known limitations.

Dataflow supports a number of storage service connectors. The following connectors have been verified to work with Dataflow inside a service perimeter:

• Cloud Storage (Java , Python )
• BigQuery (Java, Python )
• Pub/Sub ( Java , Python )
• Bigtable (Java )
• Spanner (Java )

For more information about Dataflow, refer to the product documentation.

• Custom BIND is not supported when using Dataflow. To customize DNS resolution when using Dataflow with VPC Service Controls, use Cloud DNS private zones instead of using custom BIND servers. To use your own on-premises DNS resolution, consider using a Google Cloud DNS forwarding method.

• Vertical Autoscaling cannot be protected by a VPC Service Controls perimeter. To use Vertical Autoscaling in a VPC Service Controls perimeter, you must disable the VPC accessible services feature.

• If you enable Dataflow Prime and launch a new job within a VPC Service Controls perimeter, the job uses Dataflow Prime without Vertical Autoscaling.

• Not all storage service connectors have been verified to work when used with Dataflow inside a service perimeter. For a list of verified connectors, see "Details" in the previous section.

• When using Python 3.5 with Apache Beam SDK 2.20.0‑2.22.0, Dataflow jobs will fail at startup if the workers have private IP addresses only, such as when using VPC Service Controls to protect resources. If Dataflow workers can only have private IP addresses, such as when using VPC Service Controls to protect resources, do not use Python 3.5 with Apache Beam SDK 2.20.0‑2.22.0. This combination causes jobs to fail at startup.

The API for Dataplex can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Dataplex, refer to the product documentation.

Dataproc requires special steps to protect using VPC Service Controls.

For more information about Dataproc, refer to the product documentation.

To protect a Dataproc cluster with a service perimeter, follow the Dataproc and VPC Service Controls networks instructions.

Dataproc Serverless requires special steps to protect using VPC Service Controls.

For more information about Dataproc Serverless for Spark, refer to the product documentation.

To protect your serverless workload with a service perimeter, follow the Dataproc Serverless and VPC Service Controls networks instructions.

The API for Dataproc Metastore can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Dataproc Metastore, refer to the product documentation.

The Dataproc Metastore integration with VPC Service Controls has no known limitations.

The API for Datastream can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Datastream, refer to the product documentation.

The Datastream integration with VPC Service Controls has no known limitations.

The API for Database Migration Service can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Database Migration Service, refer to the product documentation.

The API for Dialogflow can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Dialogflow, refer to the product documentation.

The API for Sensitive Data Protection can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Sensitive Data Protection, refer to the product documentation.

The API for Cloud DNS can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud DNS, refer to the product documentation.

• You can access Cloud DNS through the restricted VIP. However you cannot create or update public DNS zones within projects inside the VPC Service Controls perimeter.

The API for Document AI can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Document AI, refer to the product documentation.

The Document AI integration with VPC Service Controls has no known limitations.

The API for Document AI Warehouse can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Document AI Warehouse, refer to the product documentation.

The Document AI Warehouse integration with VPC Service Controls has no known limitations.

The API for Cloud Domains can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Domains, refer to the product documentation.

• The contact data used in Cloud Domains might be shared with the domain ending or top-level domain (TLD) registry and might be publicly accessible for WHOIS/RDAP as your settings permit, in compliance with ICANN rules. For details, see Privacy protection.

• The DNS configuration data used in Cloud Domains—name servers and DNSSEC settings—is public. If your domain delegates to a public DNS zone, which is the default, then that zone's DNS configuration data is public too.

An Eventarc Advanced bus outside of a service perimeter can't receive events from Google Cloud projects inside the perimeter. An Eventarc Advanced bus inside of a perimeter can't route events to a consumer outside of the perimeter.

• To publish to an Eventarc Advanced bus, the source of an event must be inside the same service perimeter as the bus.
• To consume a message, an event consumer must be inside the same service perimeter as the bus.

For more information about Eventarc Advanced, refer to the product documentation.

Eventarc Standard handles event delivery using Pub/Sub topics and push subscriptions. To access the Pub/Sub API and manage event triggers, the Eventarc API must be protected within the same VPC Service Controls service perimeter as the Pub/Sub API.

For more information about Eventarc Standard, refer to the product documentation.

The API for Distributed Cloud Edge Network API can be protected by VPC Service Controls and used normally inside service perimeters.

For more information about Distributed Cloud Edge Network API, refer to the product documentation.

The Distributed Cloud Edge Network API integration with VPC Service Controls has no known limitations.

The API for Anti Money Laundering AI can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Anti Money Laundering AI, refer to the product documentation.

The Anti Money Laundering AI integration with VPC Service Controls has no known limitations.

When you configure and exchange Firebase App Check tokens, VPC Service Controls protects only the Firebase App Check service. To protect services that rely on Firebase App Check, you must set up service perimeters for those services.

For more information about Firebase App Check, refer to the product documentation.

The Firebase App Check integration with VPC Service Controls has no known limitations.

When you manage Firebase Security Rules policies VPC Service Controls protects only the Firebase Security Rules service. To protect services that rely on Firebase Security Rules, you must set up service permiters for those services.

For more information about Firebase Security Rules, refer to the product documentation.

The Firebase Security Rules integration with VPC Service Controls has no known limitations.

See the Cloud Run functions documentation for setup steps. VPC Service Controls protection does not apply to the build phase when Cloud Run functions are built using Cloud Build. For more details, see the known limitations.

For more information about Cloud Run functions, refer to the product documentation.

When you restrict IAM with a perimeter, only actions that use the IAM API are restricted. These actions include managing custom IAM roles, managing workload identity pools, and managing service accounts and keys. The perimeter doesn't restrict workforce pools actions because workforce pools are organization-level resources.

The perimeter around IAM doesn't restrict access management (that is, getting or setting IAM policies) for resources owned by other services, like Resource Manager projects, folders, and organizations or Compute Engine virtual machine instances. To restrict access management for these resources, create a perimeter that restricts the service that owns the resources. For a list of resources that accept IAM policies and the services that own them, see Resource types that accept IAM policies.

Additionaly, the perimeter around IAM doesn't restrict actions that use other APIs, including the following:

• IAM Policy Simulator API
• IAM Policy Troubleshooter API
• Security Token Service API
• Service Account Credentials API (including the legacy signBlob and signJwt methods in the IAM API)

For more information about Identity and Access Management, refer to the product documentation.

If you are inside the perimeter, you cannot call the roles.list method with an empty string to list IAM predefined roles. If you need to view predefined roles, see IAM role documentation.

IAP Admin API enables users to configure IAP.

For more information about IAP Admin API , refer to the product documentation.

The IAP Admin API integration with VPC Service Controls has no known limitations.

The API for Cloud KMS Inventory API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud KMS Inventory API, refer to the product documentation.

The SearchProtectedResources API method does not enforce service perimeter restrictions on returned projects.

The API for Service Account Credentials can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Service Account Credentials, refer to the product documentation.

The Service Account Credentials integration with VPC Service Controls has no known limitations.

The API for Service Metadata API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Service Metadata API, refer to the product documentation.

The Service Metadata API integration with VPC Service Controls has no known limitations.

The API for Serverless VPC Access can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Serverless VPC Access, refer to the product documentation.

The Serverless VPC Access integration with VPC Service Controls has no known limitations.

The Cloud KMS API can be protected by VPC Service Controls and the product can be used inside service perimeters. The access to Cloud HSM services is also protected by VPC Service Controls and can be used inside service perimeters.

For more information about Cloud Key Management Service, refer to the product documentation.

The Cloud Key Management Service integration with VPC Service Controls has no known limitations.

The API for Game Servers can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Game Servers, refer to the product documentation.

The Game Servers integration with VPC Service Controls has no known limitations.

The API for Gemini Code Assist can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Gemini Code Assist, refer to the product documentation.

Access control based on device, public IP address, or location is not supported for Gemini in the Google Cloud console.

The API for Identity-Aware Proxy for TCP can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Identity-Aware Proxy for TCP, refer to the product documentation.

The API for Cloud Life Sciences can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Life Sciences, refer to the product documentation.

The Cloud Life Sciences integration with VPC Service Controls has no known limitations.

Additional configuration required for:

• On-premises access to the Managed Microsoft AD API
• Shared VPC

For more information about Managed Service for Microsoft Active Directory, refer to the product documentation.

The Managed Service for Microsoft Active Directory integration with VPC Service Controls has no known limitations.

The API for reCAPTCHA can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about reCAPTCHA, refer to the product documentation.

The reCAPTCHA integration with VPC Service Controls has no known limitations.

The API for Web Risk can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Web Risk, refer to the product documentation.

The Evaluate API and the Submission API are not supported by VPC Service Controls.

The API for Recommender can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Recommender, refer to the product documentation.

• VPC Service Controls doesn't support organization, folder, or billing account resources.

The API for Secret Manager can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Secret Manager, refer to the product documentation.

The Secret Manager integration with VPC Service Controls has no known limitations.

VPC Service Controls protection applies to all administrator operations, publisher operations, and subscriber operations (except for existing push subscriptions).

For more information about Pub/Sub, refer to the product documentation.

In projects protected by a service perimeter, the following limitations apply:

• New push subscriptions can't be created unless the push endpoints are set to Cloud Run services with default run.app URLs or a Workflows execution (custom domains don't work). For more information about integrating with Cloud Run, see Using VPC Service Controls.
• For non-push subscriptions, you must create a subscription in the same perimeter as the topic or enable egress rules to allow access from the topic to the subscription.
• When routing events through Eventarc to Workflows targets for which the push endpoint is set to a Workflows execution, you can only create new push subscriptions through Eventarc.
• Pub/Sub subscriptions created prior to the service perimeter are not blocked.

VPC Service Controls protection applies to all subscriber operations.

For more information about Pub/Sub Lite, refer to the product documentation.

The Pub/Sub Lite integration with VPC Service Controls has no known limitations.

Use VPC Service Controls with Cloud Build private pools to add additional security to your builds.

For more information about Cloud Build, refer to the product documentation.

• VPC Service Controls protection is available only for builds run in private pools.

• Cloud Build Pub/Sub triggers are not supported.

The API for Cloud Deploy can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Deploy, refer to the product documentation.

To use Cloud Deploy in a perimeter, you must use a Cloud Build private pool for the target's execution environments. Don't use the default (Cloud Build) worker pool, and don't use a hybrid pool.

Configuring Composer for use with VPC Service Controls

For more information about Cloud Composer, refer to the product documentation.

• Enabling DAG serialization prevents Airflow from displaying a rendered template with functions in the web UI.

• Setting the async_dagbag_loader flag to True is not supported while DAG serialization is enabled.

• Enabling DAG serialization disables all Airflow web server plugins, as they could risk the security of the VPC network where Cloud Composer is deployed. This doesn't impact the behaviour of scheduler or worker plugins, including Airflow operators and sensors.

• When Cloud Composer is running inside a perimeter, access to public PyPI repositories is restricted. In the Cloud Composer documentation, see Installing Python dependencies to learn how to install PyPi modules in Private IP mode.

The API for Cloud Quotas can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Quotas, refer to the product documentation.

For more information about Cloud Run, refer to the product documentation.

• Cloud Scheduler job creation
• Cloud Scheduler job updates

For more information about Cloud Scheduler, refer to the product documentation.

The API for Spanner can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Spanner, refer to the product documentation.

The Spanner integration with VPC Service Controls has no known limitations.

The API for Speaker ID can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Speaker ID, refer to the product documentation.

The Speaker ID integration with VPC Service Controls has no known limitations.

The API for Cloud Storage can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Storage, refer to the product documentation.

The API for Cloud Tasks can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

HTTP requests from Cloud Tasks executions are supported as follows:

• Authenticated requests to VPC Service Controls-compliant Cloud Run functions and Cloud Run endpoints are allowed.
• Requests to non-Cloud Run functions and non-Cloud Run endpoints are blocked.
• Requests to non-VPC Service Controls-compliant Cloud Run functions and Cloud Run endpoints are blocked.

For more information about Cloud Tasks, refer to the product documentation.

VPC Service Controls perimeters protect the Cloud SQL Admin API.

For more information about Cloud SQL, refer to the product documentation.

• Service perimeters protect only the Cloud SQL Admin API. They do not protect IP-based data access to Cloud SQL instances. You need to use an organization policy constraint to restrict public IP access on Cloud SQL instances.
• Before you configure VPC Service Controls for Cloud SQL, enable the Service Networking API.

• Cloud SQL imports and exports can only perform reads and writes from a Cloud Storage bucket within the same service perimeter as the Cloud SQL replica instance.

• In the external server migration flow, you need to add the Cloud Storage bucket to the same service perimeter.
• In the key creation flow for CMEK, you need to create the key in the same service perimeter as the resources that use it.
• When restoring an instance from a backup, the target instance needs to reside in the same service perimeter as the backup.

The API for Video Intelligence API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Video Intelligence API, refer to the product documentation.

The Video Intelligence API integration with VPC Service Controls has no known limitations.

The API for Cloud Vision API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Vision API, refer to the product documentation.

To use Artifact Analysis with VPC Service Controls, you may have to add other services to your VPC perimeter:

• If you are using Pub/Sub notifications with Artifact Analysis, add Pub/Sub to your service perimeter.
• If you are using the Container Scanning API, add your registry to the perimeter: Artifact Registry or Container Registry.

Because the Container Scanning API is a surfaceless API that stores the results in Artifact Analysis, you do not need to protect the API with a service perimeter.

For more information about Artifact Analysis, refer to the product documentation.

The Artifact Analysis integration with VPC Service Controls has no known limitations.

In addition to protecting the Container Registry API, Container Registry can be used inside a service perimeter with GKE and Compute Engine.

For more information about Container Registry, refer to the product documentation.

• When you specify an ingress or egress policy for a service perimeter, you cannot use ANY_SERVICE_ACCOUNT and ANY_USER_ACCOUNT as an identity type for all Container Registry operations.

  As a workaround, use ANY_IDENTITY as the identity type.

• Because Container Registry uses the gcr.io domain, you must configure DNS for *.gcr.io to map to either private.googleapis.com or restricted.googleapis.com. For more information, see Securing Container Registry in a service perimeter.

• In addition to the containers inside a perimeter that are available to Container Registry, the following read-only repositories are available to all projects regardless of any restrictions enforced by service perimeters:

  • gcr.io/anthos-baremetal-release
  • gcr.io/asci-toolchain
  • gcr.io/cloud-airflow-releaser
  • gcr.io/cloud-builders
  • gcr.io/cloud-dataflow
  • gcr.io/cloud-ingest
  • gcr.io/cloud-marketplace
  • gcr.io/cloud-ssa
  • gcr.io/cloudsql-docker
  • gcr.io/config-management-release
  • gcr.io/deeplearning-platform-release
  • gcr.io/foundry-dev
  • gcr.io/fn-img
  • gcr.io/gae-runtimes
  • gcr.io/serverless-runtimes
  • gcr.io/gke-node-images
  • gcr.io/gke-release
  • gcr.io/gkeconnect
  • gcr.io/google-containers
  • gcr.io/kubeflow
  • gcr.io/kubeflow-images-public
  • gcr.io/kubernetes-helm
  • gcr.io/istio-release
  • gcr.io/ml-pipeline
  • gcr.io/projectcalico-org
  • gcr.io/rbe-containers
  • gcr.io/rbe-windows-test-images
  • gcr.io/speckle-umbrella
  • gcr.io/stackdriver-agents
  • gcr.io/tensorflow
  • gcr.io/vertex-ai
  • gcr.io/vertex-ai-restricted
  • gke.gcr.io
  • k8s.gcr.io

  In all cases, the multi-regional versions of these repositories are also available.

The API for Google Kubernetes Engine can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Google Kubernetes Engine, refer to the product documentation.

• To fully protect the Google Kubernetes Engine API, you must include the Kubernetes Metadata API (kubernetesmetadata.googleapis.com) as well in your perimeter.
• Only private clusters can be protected using VPC Service Controls. Clusters with public IP addresses are not supported by VPC Service Controls.

• Autoscaling works independent of GKE. Because VPC Service Controls doesn't support autoscaling.googleapis.com, autoscaling doesn't work. When you use GKE, you can ignore the SERVICE_NOT_ALLOWED_FROM_VPC violation in the audit logs that is caused due to the autoscaling.googleapis.com service.

The API for Container Security API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Container Security API, refer to the product documentation.

The Container Security API integration with VPC Service Controls has no known limitations.

Image streaming is a GKE data streaming feature that provides shorter container image pull times for images stored in Artifact Registry. If VPC Service Controls protects your container images and you use Image streaming, you must also include the Image streaming API in the service perimeter.

For more information about Image streaming, refer to the product documentation.

• The following read-only repositories are available to all projects regardless of any restrictions enforced by service perimeters:

  • gcr.io/anthos-baremetal-release
  • gcr.io/asci-toolchain
  • gcr.io/cloud-airflow-releaser
  • gcr.io/cloud-builders
  • gcr.io/cloud-dataflow
  • gcr.io/cloud-ingest
  • gcr.io/cloud-marketplace
  • gcr.io/cloud-ssa
  • gcr.io/cloudsql-docker
  • gcr.io/config-management-release
  • gcr.io/deeplearning-platform-release
  • gcr.io/foundry-dev
  • gcr.io/fn-img
  • gcr.io/gae-runtimes
  • gcr.io/serverless-runtimes
  • gcr.io/gke-node-images
  • gcr.io/gke-release
  • gcr.io/gkeconnect
  • gcr.io/google-containers
  • gcr.io/kubeflow
  • gcr.io/kubeflow-images-public
  • gcr.io/kubernetes-helm
  • gcr.io/istio-release
  • gcr.io/ml-pipeline
  • gcr.io/projectcalico-org
  • gcr.io/rbe-containers
  • gcr.io/rbe-windows-test-images
  • gcr.io/speckle-umbrella
  • gcr.io/stackdriver-agents
  • gcr.io/tensorflow
  • gcr.io/vertex-ai
  • gcr.io/vertex-ai-restricted
  • gke.gcr.io
  • k8s.gcr.io

Fleet management APIs, including the Connect gateway, can be protected with VPC Service Controls, and fleet management features can be used normally inside service perimeters. For more information, see the following:

• Use VPC Service Controls with the Connect Agent
• Use VPC Service Controls with the Connect gateway

For more information about Fleets, refer to the product documentation.

• Although all fleet management features can be used normally, enabling a service perimeter around the Stackdriver API restricts the Policy Controller fleet feature from integrating with Security Command Center.
• When using the Connect gateway to access GKE clusters, VPC Service Controls perimeter for container.googleapis.com is not enforced.

The following Cloud Resource Manager API methods can be protected by VPC Service Controls:

• v1 project.setIAMPolicy
• v1beta1 project.setIAMPolicy
• v3 tagKeys.*
• v3 tagValues.*
• v3 tagValues.tagHolds.*
• v3 tagBindings.*

For more information about Resource Manager, refer to the product documentation.

• Only tag keys directly parented by a project resource and corresponding tag values can be protected using VPC Service Controls. When a project is added to a VPC Service Controls perimeter, all tag keys and corresponding tag values under the project are considered to be resources within the perimeter.
• Tag keys parented by an organization resource and their corresponding tag values can't be included in a VPC Service Controls perimeter and can't be protected using VPC Service Controls.
• Clients inside a VPC Service Controls perimeter can't access tag keys and corresponding values parented by an organization resource, unless an egress rule allowing access is set on the perimeter. For more information about setting egress rules, see Ingress and egress rules.
• Tag bindings are considered resources within the same perimeter as the resource to which the tag value is bound. For example, the tag bindings on a Compute Engine instance in a project is considered to belong to that project regardless of where the tag key is defined.
• Some services such as Compute Engine allow creating tag bindings using their own service APIs, in addition to the Resource Manager service APIs. For example, adding tags to a Compute Engine VM during resource creation. To protect tag bindings created or deleted using these service APIs, add the corresponding service, such as compute.googleapis.com, to the list of restricted services in the perimeter.
• Tags support method-level restrictions, so you can scope the method_selectors to specific API methods. For a list of restrictable methods, see Supported service method restrictions.
• Granting the owner role on a project through Google Cloud console is now supported by VPC Service Controls. You cannot send an owner invitation or accept an invitation outside service perimeters. If you try to accept an invitation from outside the perimeter you will not be granted the owner role and there will not be any error or warning message displayed.

The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Logging, refer to the product documentation.

The API for Certificate Manager can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Certificate Manager, refer to the product documentation.

The Certificate Manager integration with VPC Service Controls has no known limitations.

The API for Cloud Monitoring can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Monitoring, refer to the product documentation.

The API for Cloud Profiler can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Profiler, refer to the product documentation.

The Cloud Profiler integration with VPC Service Controls has no known limitations.

The API for Timeseries Insights API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Timeseries Insights API, refer to the product documentation.

The Timeseries Insights API integration with VPC Service Controls has no known limitations.

The API for Cloud Trace can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Trace, refer to the product documentation.

The Cloud Trace integration with VPC Service Controls has no known limitations.

The API for Cloud TPU can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud TPU, refer to the product documentation.

The Cloud TPU integration with VPC Service Controls has no known limitations.

For more information about Natural Language API, refer to the product documentation.

Because Natural Language API is a stateless API and doesn't run on projects, using VPC Service Controls to protect Natural Language API does not have any effect.

The API for Network Connectivity Center can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Network Connectivity Center, refer to the product documentation.

The Network Connectivity Center integration with VPC Service Controls has no known limitations.

The API for Cloud Asset API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Asset API, refer to the product documentation.

• VPC Service Controls doesn't support access to folder-level or organization-level Cloud Asset API resources from resources and clients inside a service perimeter. VPC Service Controls protects project-level Cloud Asset API resources. You can specify an egress policy to prevent access to project-level Cloud Asset API resources from projects inside the perimeter.
• VPC Service Controls doesn't support adding folder-level or organization-level Cloud Asset API resources into a service perimeter. You cannot use a perimeter to protect folder-level or organization-level Cloud Asset API resources. To manage Cloud Asset Inventory permissions at the folder or organization level, we recommend using IAM.

The API for Speech-to-Text can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Speech-to-Text, refer to the product documentation.

The Speech-to-Text integration with VPC Service Controls has no known limitations.

The API for Text-to-Speech can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Text-to-Speech, refer to the product documentation.

The Text-to-Speech integration with VPC Service Controls has no known limitations.

The API for Translation can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Translation, refer to the product documentation.

Cloud Translation - Advanced (v3) supports VPC Service Controls but not Cloud Translation - Basic (v2). To apply VPC Service Controls, you must use Cloud Translation - Advanced (v3). For more information about the different editions, see Compare Basic and Advanced.

Use VPC Service Controls with the Live Stream API to secure your pipeline.

For more information about Live Stream API, refer to the product documentation.

To protect input endpoints with a service perimeter, you must follow the instructions for setting up a private pool and send input video streams over a private connection.

The API for Transcoder API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Transcoder API, refer to the product documentation.

The Transcoder API integration with VPC Service Controls has no known limitations.

The API for Video Stitcher API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Video Stitcher API, refer to the product documentation.

The Video Stitcher API integration with VPC Service Controls has no known limitations.

The API for Access Approval can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Access Approval, refer to the product documentation.

The Access Approval integration with VPC Service Controls has no known limitations.

The API for Cloud Healthcare API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Healthcare API, refer to the product documentation.

VPC Service Controls doesn't support customer-managed encryption keys (CMEK) in the Cloud Healthcare API.

We recommend placing your Storage Transfer Service project within the same service perimeter as your Cloud Storage resources. This protects both your transfer and your Cloud Storage resources. Storage Transfer Service also supports scenarios where the Storage Transfer Service project is not in the same perimeter as your Cloud Storage buckets, using an egress policy.

For setup information, see Using Storage Transfer Service with VPC Service Controls

Transfer service for on-premises data

See Using Transfer for on-premises with VPC Service Controls for details and setup information for Transfer for on-premises.

For more information about Storage Transfer Service, refer to the product documentation.

The API for Service Control can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Service Control, refer to the product documentation.

• When you call the Service Control API from a VPC network in a service perimeter with Service Control restricted to report billing or analytics metrics, you can only use the Service Control report method to report metrics for VPC Service Controls supported services.

The API for Memorystore for Redis can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Memorystore for Redis, refer to the product documentation.

• Service perimeters protect only the Memorystore for Redis API. Perimeters do not protect normal data access on Memorystore for Redis instances within the same network.

• If the Cloud Storage API is also protected, then Memorystore for Redis import and export operations can only read and write to a Cloud Storage bucket within the same service perimeter as the Memorystore for Redis instance.

• If you use both Shared VPC and VPC Service Controls, you must have the host project that provides the network and the service project that contains the Redis instance inside the same perimeter in order for Redis requests to succeed. At any time, separating the host project and service project with a perimeter can cause a Redis instance failure, in addition to blocked requests. For more information, see Memorystore for Redis configuration requirements.

The API for Memorystore for Memcached can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Memorystore for Memcached, refer to the product documentation.

• Service perimeters protect only the Memorystore for Memcached API. Perimeters do not protect normal data access on Memorystore for Memcached instances within the same network.

The API for Service Directory can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Service Directory, refer to the product documentation.

The Service Directory integration with VPC Service Controls has no known limitations.

To fully protect the Visual Inspection AI, include all of the following APIs in your perimeter:

• Visual Inspection AI API (visualinspection.googleapis.com)
• Vertex AI API (aiplatform.googleapis.com)
• Cloud Storage API (storage.googleapis.com)
• Artifact Registry API (artifactregistry.googleapis.com)
• Container Registry API (containerregistry.googleapis.com)

For more information about Visual Inspection AI, refer to the product documentation.

The Visual Inspection AI integration with VPC Service Controls has no known limitations.

Transfer Appliance is fully supported for projects using VPC Service Controls.

Transfer Appliance doesn't offer an API, and therefore does not support API-related features in VPC Service Controls.

For more information about Transfer Appliance, refer to the product documentation.

• When Cloud Storage is protected by VPC Service Controls, the Cloud KMS key you share with the Transfer Appliance Team must be within the same project as the destination Cloud Storage bucket.

The API for Organization Policy Service can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Organization Policy Service, refer to the product documentation.

VPC Service Controls doesn't support access restrictions to folder-level or organization-level organization policies that are inherited by the project. VPC Service Controls protects project-level Organization Policy Service API resources.

For example, if an ingress rule restricts a user from accessing the Organization Policy Service API, that user gets a 403 error when querying for organization policies enforced on the project. However, the user is still able to access the organization policies of the folder and organization containing the project.

You can call the OS Login API from within VPC Service Controls perimeters. To manage OS Login from within VPC Service Controls perimeters, set up OS Login.

SSH connections to VM instances are not protected by VPC Service Controls.

For more information about OS Login, refer to the product documentation.

The OS Login methods for reading and writing SSH keys don't enforce VPC Service Controls perimeters. Use VPC accessible services to disable access to OS Login APIs.

The API for Personalized Service Health can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Personalized Service Health, refer to the product documentation.

VPC Service Controls does not support the OrganizationEvents and OrganizationImpacts resources of the Service Health API. Therefore, VPC Service Controls policy checks won't occur when you call the methods for these resources. However, you can call the methods from a service perimeter using a restricted VIP.

You can call the OS Config API from within VPC Service Controls perimeters. To use VM Manager from within VPC Service Controls perimeters, set up VM Manager.

For more information about VM Manager, refer to the product documentation.

Workflows is an orchestration platform that can combine Google Cloud services and HTTP-based APIs to execute services in an order that you define.

When you protect the Workflows API using a service perimeter, the Workflow Executions API is also protected. You do not need to separately add workflowexecutions.googleapis.com to your perimeter's list of protected services.

HTTP requests from a Workflows execution are supported as follows:

• Authenticated requests to VPC Service Controls-compliant Google Cloud endpoints are allowed.
• Requests to Cloud Run functions and Cloud Run service endpoints are allowed.
• Requests to third-party endpoints are blocked.
• Requests to non-VPC Service Controls-compliant Google Cloud endpoints are blocked.

For more information about Workflows, refer to the product documentation.

The Workflows integration with VPC Service Controls has no known limitations.

The API for Filestore can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Filestore, refer to the product documentation.

• Service perimeters protect only the Filestore API. Perimeters do not protect normal NFS data access on Filestore instances within the same network.

• If you use both Shared VPC and VPC Service Controls, you must have the host project that provides the network and the service project that contains the Filestore instance inside the same perimeter for the Filestore instance to function correctly. Separating the host project and service project with a perimeter might cause the existing instances to become unavailable and might not create new instances.

For more information about Parallelstore, refer to the product documentation.

• If you use both Shared VPC and VPC Service Controls, you must have the host project that provides the network and the service project that contains the Parallelstore instance inside the same perimeter for the Parallelstore instance to function correctly. Separating the host project and service project with a perimeter might cause the existing instances to become unavailable and might not create new instances.

The API for Container Threat Detection can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Container Threat Detection, refer to the product documentation.

The Container Threat Detection integration with VPC Service Controls has no known limitations.

For more information about Ads Data Hub, refer to the product documentation.

VPC Service Controls only restricts token exchanges if the audience in the request is a project-level resource. For example, VPC Service Controls doesn't restrict requests for downscoped tokens, because those requests have no audience. VPC Service Controls also doesn't restrict requests for Workforce Identity Federation because the audience is an organization-level resource.

For more information about Security Token Service, refer to the product documentation.

The firestore.googleapis.com, datastore.googleapis.com, and firestorekeyvisualizer.googleapis.com services are bundled together. When you restrict the firestore.googleapis.com service in a perimeter, the perimeter also restricts the datastore.googleapis.com and firestorekeyvisualizer.googleapis.com services.

To restrict datastore.googleapis.com service, use the firestore.googleapis.com service name.

To get full egress protection on import and export operations, you must use the Firestore service agent. See the following for more information:

• Securing Firestore import and export operations with VPC Service Controls.
• Securing Datastore import and export operations with VPC Service Controls.

For more information about Firestore/Datastore, refer to the product documentation.

The API for Migrate to Virtual Machines can be protected by VPC Service Controls, and the product can be used normally inside service perimeters.

For more information about Migrate to Virtual Machines, refer to the product documentation.

• To fully protect Migrate to Virtual Machines, add all of the following APIs to the service perimeter:

  • Artifact Registry API (artifactregistry.googleapis.com)
  • Pub/Sub API (pubsub.googleapis.com)
  • Cloud Storage API (storage.googleapis.com)
  • Cloud Logging API (logging.googleapis.com)
  • Container Registry API (containerregistry.googleapis.com)
  • Secret Manager API (secretmanager.googleapis.com)
  • Compute Engine API (compute.googleapis.com)

  For more information, see the Migrate to Virtual Machines documentation.

VPC Service Controls lets you protect the infrastructure data that you collect with Migration Center with a service perimeter.

For more information about Migration Center, refer to the product documentation.

The API for Backup and DR Service can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Backup and DR Service, refer to the product documentation.

If you remove the internet default route from the service producer project using the command gcloud services vpc-peerings enable-vpc-service-controls, then you may not be able to access or deploy the management console. If you encounter this issue, contact Google Cloud Customer Care.

You can use VPC Service Controls to protect backup for GKE and you can use backup for GKE features normally inside service perimeters.

For more information about Backup for GKE, refer to the product documentation.

The Backup for GKE integration with VPC Service Controls has no known limitations.

The API for Retail API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Retail API, refer to the product documentation.

The Retail API integration with VPC Service Controls has no known limitations.

Application Integration is a collaborative workflow management system that allows you to create, augment, debug and understand core business system workflows. The workflows on the Application Integration are made up of triggers and tasks. There are several kinds of triggers such as api trigger/Pub/Sub trigger/cron trigger/sfdc trigger.

For more information about Application Integration, refer to the product documentation.

The API for Integration Connectors can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Integration Connectors, refer to the product documentation.

The API for Error Reporting can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Error Reporting, refer to the product documentation.

The API for Cloud Workstations can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Workstations, refer to the product documentation.

• To fully protect Cloud Workstations, you must restrict the Compute Engine API in your service perimeter whenever you restrict the Cloud Workstations API.
• Ensure that Google Cloud Storage API, Google Container Registry API, and Artifact Registry API are VPC accessible in your service perimeter. This is needed to pull images onto your workstation. We also recommended that you allow Cloud Logging API and Cloud Error Reporting API to be VPC accessible in your service perimeter, although this is not required to use Cloud Workstations.
• Ensure that your workstation cluster is private. Configuring a private cluster prevents connections to your workstations from outside your VPC service perimeter.
• Ensure that you disable public IP addresses in your workstation configuration. Failing to do so results in VMs with public IP addresses in your project. We strongly recommend that you use the constraints/compute.vmExternalIpAccess organization policy constraint to disable public IP addresses for all VMs in your VPC service perimeter. For details, see Restricting external IP addresses to specific VMs.
• While connecting to your workstation, access control is only based on whether the private network you are connecting from belongs to the security perimeter. Access control based on device, public IP address, or location is not supported.

The API for Cloud IDS can be protected by VPC Service Controls, and the product can be used normally inside service perimeters.

For more information about Cloud IDS, refer to the product documentation.

Cloud IDS uses Cloud Logging to create threat logs in your project. If Cloud Logging is restricted by the service perimeter, VPC Service Controls blocks the Cloud IDS threat logs, even if Cloud IDS is not added as a restricted service to the perimeter. To use Cloud IDS inside a service perimeter, you must configure an ingress rule for the Cloud Logging service account in your service perimeter.

For more information about Chrome Enterprise Premium, refer to the product documentation.

The Chrome Enterprise Premium integration with VPC Service Controls has no known limitations.

When you restrict the Policy Troubleshooter API with a perimeter, principals can troubleshoot IAM allow policies only if all resources involved in the request are in the same perimeter. There are usually two resources involved in a troubleshooting request:

• The resource you're troubleshooting access for. This resource can be any type. You explicitly specify this resource when you troubleshoot an allow policy.

• The resource you're using to troubleshoot access. This resource is a project, folder, or organization. In the Google Cloud console and gcloud CLI, this resource is inferred based on the project, folder, or organization you have selected. In the REST API, you specify this resource using the x-goog-user-project header.

  This resource can be the same as the resource that you're troubleshooting access for, but it doesn't need to be.

If these resources aren't in the same perimeter, the request fails.

For more information about Policy Troubleshooter, refer to the product documentation.

The Policy Troubleshooter integration with VPC Service Controls has no known limitations.

When you restrict the Policy Simulator API with a perimeter, principals can simulate allow policies only if certain resources involved in the simulation are in the same perimeter. There are several resources involved in a simulation:

• The resource whose allow policy you're simulating. This resource is also called the target resource. In the Google Cloud console, this is the resource whose allow policy you're editing. In the gcloud CLI and REST API, you explicitly specify this resource when you simulate an allow policy.

• The project, folder, or organization that creates and runs the simulation. This resource is also called the host resource. In the Google Cloud console and gcloud CLI, this resource is inferred based on the project, folder, or organization you have selected. In the REST API, you specify this resource using the x-goog-user-project header.

  This resource can be the same as the resource that you're simulating access for, but it doesn't need to be.

• The resource that provides access logs for the simulation. In a simulation, there is always one resource that provides access logs for the simulation. This resource varies depending on the target resource type:

  • If you are simulating an allow policy for a project or organization, Policy Simulator retrieves the access logs for that project or organization.
  • If you are simulating an allow policy for a different type of resource, Policy Simulator retrieves the access logs for that resource's parent project or organization.
  • If you are simulating multiple resources' allow policies at once, Policy Simulator retrieves the access logs for the resources' nearest common project or organization.
• All supported resources with relevant allow policies. When Policy Simulator runs a simulation, it considers all allow policies that might impact the user's access, including allow policies on the target resource's ancestor and descendant resources. As a result, these ancestor and descendant resources are also involved in simulations.

If the target resource and the host resource aren't in the same perimeter, the request fails.

If the target resource and the resource that provides access logs for the simulation aren't in the same perimeter, the request fails.

If the target resource and some supported resources with relevant allow policies aren't in the same perimeter, the requests succeeds, but the results might be incomplete. For example, if you're simulating a policy for a project in a perimeter, the results won't include the allow policy of the project's parent organization, because organizations are always outside of VPC Service Controls perimeters. To get more complete results, you can configure ingress and egress rules for the perimeter.

For more information about Policy Simulator, refer to the product documentation.

The Policy Simulator integration with VPC Service Controls has no known limitations.

The API for Essential Contacts can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Essential Contacts, refer to the product documentation.

The Essential Contacts integration with VPC Service Controls has no known limitations.

The API for Identity Platform can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Identity Platform, refer to the product documentation.

• To fully protect Identity Platform, add the Secure Token API (securetoken.googleapis.com) to the service perimeter to allow token refresh. securetoken.googleapis.com is not listed on the VPC Service Controls page of the Google Cloud console. You can only add this service with the gcloud access-context-manager perimeters update command.

• If your application also integrates with the blocking functions feature, add Cloud Run functions (cloudfunctions.googleapis.com) to the service perimeter.

• The use of SMS-based multi-factor authentication (MFA), email authentication, or third-party identity providers causes data to be sent out of the perimeter. If you don't use MFA with SMS, email authentication, or third-party identity providers, disable these features.

The API for GKE Multi-Cloud can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about GKE Multi-Cloud, refer to the product documentation.

• To fully protect the GKE Multi-Cloud API, you must include the Kubernetes Metadata API (kubernetesmetadata.googleapis.com) as well in your perimeter.

The Anthos On-Prem API can be protected by VPC Service Controls, and the API can be used normally inside service perimeters.

For more information about Anthos On-Prem API, refer to the product documentation.

• To fully protect the Anthos On-Prem API, add all of the following APIs to the service perimeter:

  • Kubernetes Metadata API (kubernetesmetadata.googleapis.com)
  • Cloud Monitoring API (monitoring.googleapis.com)
  • Cloud Logging API (logging.googleapis.com)
  Note that VPC Service Controls doesn't protect against Cloud Logging log exports on a folder or organization level.

You can create a cluster in your environment, which is connected to VPC using Cloud Interconnect or Cloud VPN.

For more information about Google Distributed Cloud (software only) for bare metal, refer to the product documentation.

• When you create or upgrade a cluster using Google Distributed Cloud (software only) for bare metal, use the flag --skip-api-check in bmctl to bypass calling the Service Usage API (serviceusage.googleapis.com), because the Service Usage API (serviceusage.googleapis.com) is not supported by VPC Service Controls. Google Distributed Cloud (software only) for bare metal invokes the Service Usage API to validate that the required APIs are enabled within a project; it is not used to validate API endpoint reachability.

• To protect your clusters, use Restricted VIP in Google Distributed Cloud (software only) for bare metal, and add all of the following APIs to the service perimeter:

• Artifact Registry API (artifactregistry.googleapis.com)
• Google Cloud Resource Manager API (cloudresourcemanager.googleapis.com)
• Compute Engine API (compute.googleapis.com)
• Connect Gateway API (connectgateway.googleapis.com)
• Google Container Registry API (containerregistry.googleapis.com)
• GKE Connect API (gkeconnect.googleapis.com)
• GKE Hub API (gkehub.googleapis.com)
• GKE On-Prem API (gkeonprem.googleapis.com)
• Cloud IAM API (iam.googleapis.com)
• Cloud Logging API (logging.googleapis.com)
• Cloud Monitoring API (monitoring.googleapis.com)
• Config Monitoring for Ops API (opsconfigmonitoring.googleapis.com)
• Service Control API (servicecontrol.googleapis.com)
• Cloud Storage API (storage.googleapis.com)

The API for On-Demand Scanning API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about On-Demand Scanning API, refer to the product documentation.

The On-Demand Scanning API integration with VPC Service Controls has no known limitations.

The API for Looker (Google Cloud core) can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Looker (Google Cloud core), refer to the product documentation.

• Only Enterprise or Embed editions of Looker (Google Cloud core) instances using private IP connections support VPC Service Controls compliance. Looker (Google Cloud core) instances with public IP connections or both public and private IP connections do not support VPC Service Controls compliance. To create an instance that uses a private IP connection, select Private IP in the Networking section of the Create instance page of the Google Cloud console.

• When placing or creating a Looker (Google Cloud core) instance inside a VPC Service Controls service perimeter, you must remove the default route to the internet by calling the services.enableVpcServiceControls method or by running the following gcloud command:
  
  gcloud services vpc-peerings enable-vpc-service-controls --network=your-network service=servicenetworking.googleapis.com
  
  Removing the default route restricts outgoing traffic to only VPC Service Controls compliant services. For example, sending email will fail because the API that is used to send email is not VPC Service Controls compliant.

• If you're using Shared VPC, ensure that you either include the Looker (Google Cloud core) service project in the same service perimeter as the Shared VPC host project or create a perimeter bridge between the two projects. If the Looker (Google Cloud core) service project and the Shared VPC host project are not in same perimeter or cannot communicate through a perimeter bridge, instance creation could fail or the Looker (Google Cloud core) instance may not function properly.

The API for Public Certificate Authority can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Public Certificate Authority, refer to the product documentation.

The Public Certificate Authority integration with VPC Service Controls has no known limitations.

The API for Storage Insights can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Storage Insights, refer to the product documentation.

The Storage Insights integration with VPC Service Controls has no known limitations.

To fully protect Dataflow Data Pipelines, include all of the following APIs in your perimeter:

• Dataflow API (dataflow.googleapis.com)
• Cloud Scheduler API (cloudscheduler.googleapis.com)
• Container Registry API (containerregistry.googleapis.com)

For more information about Dataflow Data Pipelines, refer to the product documentation.

The Dataflow Data Pipelines integration with VPC Service Controls has no known limitations.

The APIs for Security Command Center can be protected by VPC Service Controls, and Security Command Center can be used normally inside service perimeters.

The securitycenter.googleapis.com and securitycentermanagement.googleapis.com services are bundled together. When you restrict the securitycenter.googleapis.com service in a perimeter, the perimeter restricts the securitycentermanagement.googleapis.com service by default. You cannot add the securitycentermanagement.googleapis.com service to the list of restricted services in a perimeter because it is bundled with securitycenter.googleapis.com.

For more information about Security Command Center, refer to the product documentation.

• VPC Service Controls doesn't support access to folder-level or organization-level Security Command Center API resources from resources and clients inside a service perimeter. VPC Service Controls protects project-level Security Command Center API resources. You can specify an egress policy to prevent access to project-level Security Command Center API resources from projects inside the perimeter.
• VPC Service Controls doesn't support adding folder-level or organization-level Security Command Center API resources into a service perimeter. You cannot use a perimeter to protect folder-level or organization-level Security Command Center API resources. To manage Security Command Center permissions at the folder or organization level, we recommend using IAM.
• VPC Service Controls doesn't support the security posture service because security posture resources (such as postures, posture deployments, and predefined posture templates) are organization-level resources.
• You cannot export findings at the folder or organization level into destinations inside a service perimeter.
• You must enable perimeter access in the following scenarios:
  • When you enable finding notifications at the folder or organization level and the Pub/Sub topic is inside a service perimeter.
  • When you export data to BigQuery from the folder or organization level and BigQuery is inside a service perimeter.
  • When you integrate Security Command Center with a SIEM or SOAR product and the product is deployed inside a service perimeter in a Google Cloud environment. Supported SIEMs and SOARs include Splunk and IBM QRadar.

The API for Cloud Customer Care can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Cloud Customer Care, refer to the product documentation.

The API for Vertex AI Agent Builder - Vertex AI Search can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Vertex AI Agent Builder - Vertex AI Search, refer to the product documentation.

The Vertex AI Agent Builder - Vertex AI Search integration with VPC Service Controls has no known limitations.

The API for Confidential Space can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Confidential Space, refer to the product documentation.

To use VPC Service Controls protection when connecting to the serial console for a virtual machine (VM) instance, you need to specify an ingress rule for the service perimeter. When setting up the ingress rule, the access level for the source must be an IP-based value and the service name set to ssh-serialport.googleapis.com. The ingress rule is required to access the serial console even if the source request and target resource are in the same perimeter.

For more information about Serial console, refer to the product documentation.

For more information about Google Cloud VMware Engine, refer to the product documentation.

To learn how to control access to Dataform with VPC Service Controls, see Configure VPC Service Controls for Dataform.

For more information about Dataform, refer to the product documentation.

Web Security Scanner and VPC Service Controls are subject to different terms of service. Review the terms of each product for details.

Web Security Scanner sends the findings to Security Command Center on demand. You can view or download the data from the Security Command Center dashboard.

For more information about Web Security Scanner, refer to the product documentation.

The Web Security Scanner integration with VPC Service Controls has no known limitations.

• You need to configure Certificate Authority Service with a working certificate authority before creating Secure Source Manager VPC Service Controls instances.
• You need to configure Private Service Connect before accessing the Secure Source Manager VPC Service Controls instance.

For more information about Secure Source Manager, refer to the product documentation.

• SERVICE_NOT_ALLOWED_FROM_VPC audit log violation caused by GKE limitations can be ignored.
• To open the VPC Service Controls web interface with a browser, the browser needs access to the following URLs:
  • https://accounts.google.com
  • https://LOCATION_OF_INSTANCE-sourcemanagerredirector-pa.client6.google.com
    • For example, https://us-central1-sourcemanagerredirector-pa.client6.google.com
  • https://lh3.googleusercontent.com

The API for API keys can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about API keys, refer to the product documentation.

The API keys integration with VPC Service Controls has no known limitations.

The Cloud Controls Partner API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Partner console in Sovereign Controls by Partners, refer to the product documentation.

The API for Microservices can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Microservices, refer to the product documentation.

The Microservices integration with VPC Service Controls has no known limitations.

The earthengine.googleapis.com and earthengine-highvolume.googleapis.com services are bundled together. When you restrict the earthengine.googleapis.com service in a perimeter, the perimeter restricts the earthengine-highvolume.googleapis.com service by default. You cannot add the earthengine-highvolume.googleapis.com service to the list of restricted services in a perimeter because it is bundled with earthengine.googleapis.com.

For more information about Earth Engine, refer to the product documentation.

App Hub enables you to discover and organize infrastructure resources into applications. You can use VPC Service Controls perimeters to protect the App Hub resources.

For more information about App Hub, refer to the product documentation.

The Cloud Code API can be protected by VPC Service Controls. To use Gemini-powered features in Cloud Code, an ingress policy must be configured to allow traffic from IDE clients. See the Gemini documentation for details.

For more information about Cloud Code, refer to the product documentation.

The Cloud Code integration with VPC Service Controls has no known limitations.

VPC Service Controls perimeter protects the Commerce Org Governance API for Google Private Marketplace.

For more information about Commerce Org Governance API, refer to the product documentation.

To restrict the internet traffic, use organization policies. Invoke the CREATE or UPDATE methods of the Google Cloud Contact Center as a Service API to apply the organization policy constraints manually.

For more information about Google Cloud Contact Center as a Service, refer to the product documentation.

The Google Cloud Contact Center as a Service integration with VPC Service Controls has no known limitations.

The API for Privileged Access Manager can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Privileged Access Manager, refer to the product documentation.

The API for Audit Manager can be protected by VPC Service Controls and the product can be used normally inside service perimeters.

For more information about Audit Manager, refer to the product documentation.