egress rules

Related topics

• egress rules is part of VPC Service Controls From the official documentation: “VPC Service Controls uses ingress and egress rules to allow access to and from the resources and clients protected by service perimeters.”
• Compute Engine works with egress rules From the official documentation: “Egress rules only apply to targets that are network interfaces of Compute Engine instances.”
• 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 Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• 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 Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Cloud Storage works with Managed Service for Apache Spark From the official documentation: “Managed Service for Apache Spark accesses these files on Cloud Storage.”
• 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 Gemini Enterprise Agent Platform From the official documentation: “[VPC Service Controls](/vpc-service-controls/docs/overview) can help you mitigate the risk of data exfiltration from Gemini Enterprise Agent Platform.”
• Cloud Storage works with Gemini Enterprise Agent Platform From the official documentation: “When you perform custom training, Agent Platform usually loads your data from Cloud Storage.”
• Compute Engine works with Managed Service for Apache Spark From the official documentation: “Google Compute Engine provides a runtime environment for all features provided by Managed Service for Apache Spark and Gemini Enterprise Agent Platform.”
• Managed Service for Apache Spark depends on Cloud Storage From the official documentation: “Managed Service for Apache Spark uses Cloud Storage as its default distributed file system.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• VPC Service Controls secures Gemini Enterprise From the official documentation: “The connection between Agent Runtime and Gemini Enterprise is compliant with VPC Service Controls (VPC-SC), ensuring secure data exchange.”
• Artifact Registry works with Gemini Enterprise Agent Platform From the official documentation: “Agent Platform supports Gemini Enterprise Agent Platform serverless training with container images on Artifact Registry or Docker Hub.”
• BigQuery works with Managed Service for Apache Spark From the official documentation: “This means you can quickly read and write BigQuery data to and from Managed Service for Apache Spark.”
• Managed Service for Apache Spark depends on Compute Engine From the official documentation: “Managed Service for Apache Spark clusters are built on [Compute Engine](/compute) instances.”
• 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).”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories so you can run containerized workloads on virtual machine (VM) instances.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with Gemini Enterprise From the official documentation: “Discovery Engine service uploads documents and user events from Cloud Storage and BigQuery, reports results to the customer Cloud Storage bucket, writes logs to customer projects using Cloud Logging, and writes and reads metrics for customer using Cloud Monitoring.”
• BigQuery is an alternative to Managed Service for Apache Spark From the official documentation: “An Analytics Workload refers to the migration of new Data Lake and Data Warehouse environments from on-premises (e.g., Teradata, Cloudera) and cloud platforms (e.g., Snowflake, Redshift, Databricks) to BigQuery or Managed Service for Apache Spark on Google Cloud.”
• 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 Storage works with Gemini Enterprise From the official documentation: “Discovery Engine service uploads documents and user events from Cloud Storage and BigQuery, reports results to the customer Cloud Storage bucket, writes logs to customer projects using Cloud Logging, and writes and reads metrics for customer using Cloud Monitoring.”
• Compute Engine works with Gemini Enterprise From the official documentation: “This page describes how to create a data store and connect Compute Engine to Gemini Enterprise.”
• Compute Engine works with Gemini Enterprise Agent Platform From the official documentation: “Google Compute Engine provides a runtime environment for all features provided by Managed Service for Apache Spark and Gemini Enterprise Agent Platform.”
• Gemini Enterprise works with VPC Service Controls From the official documentation: “Gemini Enterprise is integrated with [VPC Service Controls](/vpc-service-controls/docs/supported-products).”
• Gemini Enterprise Agent Platform depends on Artifact Registry From the official documentation: “Certain tasks in Agent Platform require that you use additional Google Cloud products besides Agent Platform. For example, in most cases, you must use Cloud Storage and Artifact Registry when you create a custom training pipeline.”
• Gemini Enterprise Agent Platform depends on Cloud Storage From the official documentation: “Certain tasks in Agent Platform require that you use additional Google Cloud products besides Agent Platform. For example, in most cases, you must use Cloud Storage and Artifact Registry when you create a custom training pipeline.”
• Managed Service for Apache Spark works with VPC Service Controls From the official documentation: “Consider the following strategies when you use VPC-SC networks with Managed Service for Apache Spark:”
• VPC Service Controls configures Artifact Registry From the official documentation: “Manage Artifact Registry VPC Service Controls configuration for remote repositories.”
• VPC Service Controls secures Managed Service for Apache Spark From the official documentation: “In this example, a Managed Service for Apache Spark cluster is running in a project protected by VPC Service Controls.”