VPC Service Controls

Related topics

• service perimeter is part of VPC Service Controls From the official documentation: “Learn how to set up a service perimeter using VPC Service Controls.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Shared VPC works with VPC Service Controls From the official documentation: “If you use both Shared VPC and VPC Service Controls, the host project that contains the network and the service project that contains the Managed Lustre instance must both be inside the same perimeter.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Cloud Audit Logs works with VPC Service Controls From the official documentation: “VPC Service Controls integrate with Cloud Audit Logs to monitor access to the control plane.”
• Private Service Connect works with VPC Service Controls From the official documentation: “VPC Service Controls that use Private Service Connect”
• VPC Service Controls secures Artifact Registry From the official documentation: “If your VPC Service Controls settings are blocking access to Artifact Registry, you must add the Artifact Registry service to the service perimeter of your VPC Service Controls.”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• VPC Service Controls secures Gemini Enterprise Agent Platform From the official documentation: “The API for Agent Platform can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures Network Connectivity Center From the official documentation: “To further secure your NCC resources, use VPC Service Controls.”
• VPC Service Controls configures service perimeter From the official documentation: “VPC Service Controls lets you set up a service perimeter to guard against data exfiltration.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• VPC Service Controls secures Knowledge Catalog From the official documentation: “The API for Knowledge Catalog can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• BigQuery works with VPC Service Controls From the official documentation: “BigQuery integrates with VPC Service Controls to restrict access to your BigQuery resources from specific networks.”
• Cloud Logging works with VPC Service Controls From the official documentation: “This page describes how you can find VPC Service Controls errors using Cloud Logging.”
• Cloud Monitoring works with VPC Service Controls From the official documentation: “Cloud Monitoring performs the VPC perimeter check when a project is *added* to a metrics scope:”
• Cloud SQL works with VPC Service Controls From the official documentation: “Make sure that you configure VPC Service Controls so that the project that hosts the CA Service CA pool and CA<br>and the project that hosts Cloud SQL belong to the same service perimeter.”
• Gemini Enterprise Agent Platform works with VPC Service Controls From the official documentation: “For information on using Gemini Enterprise Agent Platform VPC Service Controls, see [VPC Service Controls with Gemini Enterprise Agent Platform](/gemini-enterprise-agent-platform/machine-learning/general/vpc-service-controls).”
• Knowledge Catalog works with VPC Service Controls From the official documentation: “The integration between Looker (Google Cloud core) and Knowledge Catalog supports VPC Service Controls.”
• VPC Service Controls secures Cloud Logging From the official documentation: “The API for Cloud Logging can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• VPC Service Controls secures Cloud Monitoring From the official documentation: “VPC Service Controls provides additional security for Cloud Monitoring to help mitigate the risk of data exfiltration.”
• VPC Service Controls secures Cloud Run From the official documentation: “To learn more about the security features that Cloud Run provides, use the following resources: - [Access control with Identity and Access Management (IAM)](/run/docs/securing/managing-access) - [Per-service identity](/run/docs/securing/service-identity) - [Google Cloud Armor…”
• VPC Service Controls secures Cloud Service Mesh From the official documentation: “VPC Service Controls help defend against data exfiltration attacks and prevent external attackers from accessing services inside a mesh.”
• VPC Service Controls secures GKE From the official documentation: “The Kubernetes Engine API can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Private Service Connect From the official documentation: “You can use Private Service Connect to connect to a Cloud SQL instance from multiple VPC networks.”
• BigQuery works with Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Identity and Access Management secures Cloud Service Mesh From the official documentation: “Access to Cloud Service Mesh in the Google Cloud console is controlled by [Identity and Access Management (IAM)](/iam/docs/overview).”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
• BigQuery works with Gemini Enterprise Agent Platform From the official documentation: “The BigQuery dataset stores all versions for the associated Gemini Enterprise Agent Platform dataset.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• BigQuery works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs maintain a record of Google Cloud events, including BigQuery events.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”