service perimeter

Related topics

• service perimeter is part of VPC Service Controls From the official documentation: “VPC Service Controls perimeters protect the AlloyDB API.”
• service perimeter secures BigQuery From the official documentation: “Protect the BigQuery resource by creating or updating a perimeter.”
• VPC Service Controls configures service perimeter From the official documentation: “VPC Service Controls is a Google Cloud feature that lets you set up a service perimeter and create a data transfer boundary.”
• service perimeter secures Cloud SQL From the official documentation: “During this procedure, you select the Cloud SQL projects that you want the VPC service perimeter to protect.”
• service perimeter secures Cloud Storage From the official documentation: “A service perimeter protects the Storage Transfer Service API and Cloud Storage resources.”
• service perimeter secures Compute Engine From the official documentation: “This tutorial shows you how to protect Compute Engine using a service perimeter and troubleshoot an ingress violation to allow authorized access to Compute Engine.”
• service perimeter secures AlloyDB From the official documentation: “First, you select the AlloyDB project that you want the VPC service perimeter to protect, and then you create and manage the service perimeter.”
• service perimeter secures Cloud Monitoring
• service perimeter secures Cloud Storage bucket From the official documentation: “If you use an aggregated log sink to route log entries to a [Cloud Storage bucket](/storage/docs) that is in a perimeter, then use `ANY_IDENTITY` as the identity type in the ingress rule.”
• service perimeter secures Google Cloud Storage From the official documentation: “`CLOUD_STORAGE_PERIMETER`: the ID of the perimeter protecting the Cloud Storage resources”
• service perimeter secures Sensitive Data Protection From the official documentation: “To learn how to set up a new service perimeter to prohibit external access to Sensitive Data Protection resources, follow the instructions in [Creating a service perimeter](/vpc-service-controls/docs/create-service-perimeters).”
• service perimeter secures Storage Transfer Service From the official documentation: “A service perimeter protects the Storage Transfer Service API and Cloud Storage resources.”
• Terraform configures service perimeter From the official documentation: “You can use Terraform to add a project in a folder to a service perimeter.”
• BigQuery works with Datastream From the official documentation: “Datastream supports three types of partitioning for BigQuery tables:”
• BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
• Cloud Storage works with Datastream From the official documentation: “When you stream to Cloud Storage, Datastream organizes data by object name and timestamp.”
• 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.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
• BigQuery works with Bigtable From the official documentation: “External BigQuery data source backed by Bigtable”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• 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: “This page describes how to use the mysql client, installed on a Compute Engine instance, to connect to Cloud SQL.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• Cloud Storage works with Storage Transfer Service From the official documentation: “Transfer data between Cloud Storage services such as AWS S3 and Cloud Storage.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Pub/Sub works with Sensitive Data Protection From the official documentation: “Watch the Pub/Sub topic until the DLP job finishes”
• BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Cloud Storage works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze a file on GCS.”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• 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 SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Identity and Access Management secures BigQuery From the official documentation: “Access to BigQuery data from AlloyDB is managed through IAM.”
• 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 SQL works with Datastream From the official documentation: “This page describes an example NAT VM configuration that lets Datastream privately connect to a Cloud SQL instance.”
• 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).”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Storage bucket is part of Google Cloud Storage From the official documentation: “The name of your Cloud Storage bucket.”
• Google Cloud Storage works with Storage Transfer Service From the official documentation: “We use Storage Transfer Service to transfer data from the appliance to your Cloud Storage bucket.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• 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 Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Logging works with Storage Transfer Service From the official documentation: “Enable Cloud Logging for agentless transfers, or transfers from S3-compatible sources, with `--log-actions` and `--log-action-states`.”
• Cloud Monitoring works with Dataflow From the official documentation: “Dataflow is fully integrated with Cloud Monitoring.”
• Cloud SQL works with Sensitive Data Protection From the official documentation: “Sensitive Data Protection starts identifying your Cloud SQL instances and creating a default connection for each instance.”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• AlloyDB works with BigQuery From the official documentation: “By integrating AlloyDB and BigQuery, you can achieve a seamless flow of data between your transactional database and your data warehouse, which supports real-time analytics and helps you build powerful interactive applications.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Bigtable works with Dataflow From the official documentation: “The Dataflow job then writes the transformed data to your Bigtable table.”
• Bigtable works with Identity and Access Management From the official documentation: “In Bigtable, authorization is fully integrated into Google Cloud's [IAM framework](/iam/docs) and requires minimal setup and maintenance.”