pipeline

Related topics

• Cloud Run works with pipeline From the official documentation: “You can use pipelines to filter, transform, and deliver events to target services such as Cloud Run and Workflows.”
• Customer-Managed Encryption Keys secures pipeline From the official documentation: “When you enable CMEK for an Eventarc Advanced pipeline, all messages that pass through the pipeline are fully encrypted with that CMEK key.”
• pipeline configures region From the official documentation: “All of the core data processing for Dataflow happens in the region that is specified in the pipeline code.”
• pipeline works with Workflows From the official documentation: “You can use pipelines to filter, transform, and deliver events to target services such as Cloud Run and Workflows.”
• 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”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• 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.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Customer-Managed Encryption Keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Cloud Run works with Eventarc From the official documentation: “Create a Cloud Run service as an event destination for the Eventarc trigger:”
• Customer-Managed Encryption Keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Eventarc works with Workflows From the official documentation: “This page shows you how to resolve issues that you might encounter when using Eventarc for Workflows.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Storage works with Eventarc From the official documentation: “Trigger functions from Cloud Storage using Eventarc”
• 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 works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Eventarc works with Pub/Sub From the official documentation: “Trigger functions from Pub/Sub using Eventarc”
• 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 Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
• Cloud SQL configures region From the official documentation: “When you create a Cloud SQL instance, you choose a [region](/docs/geography-and-regions) where the instance and its data are stored.”
• Pub/Sub works with Workflows From the official documentation: “Pub/Sub can be integrated into multistep serverless [Workflows](/workflows) declaratively.”
• BigQuery works with Workflows From the official documentation: “If you want to retain the information from the job for longer than 60 days, then you can export the job information to BigQuery by using Workflows.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• Customer-Managed Encryption Keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Eventarc works with GKE From the official documentation: “Before creating the service account, enable Eventarc to manage GKE clusters:”
• Eventarc depends on Pub/Sub From the official documentation: “Eventarc uses Pub/Sub as its transport layer and has a default retry policy that might not work well for your function.”
• GKE works with Pub/Sub From the official documentation: “GKE publishes upgrade notifications to [Pub/Sub](/pubsub/docs/overview), providing you with a channel to receive information from GKE about your clusters.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• 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 GKE From the official documentation: “Subsequently, by integrating BigQuery with GKE, you can use BigQuery to efficiently handle massive datasets (like Google Analytics) and the model's natural language understanding capabilities to generate meaningful insights.”
• Cloud SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with Workflows From the official documentation: “Learn how to run serverless workflows using Workflows, Cloud Functions, and Firestore to load raw data, such as event logs, from Cloud Storage to BigQuery.”
• Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
• Customer-Managed Encryption Keys secures Cloud Run From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Cloud Run.”
• Customer-Managed Encryption Keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
• Customer-Managed Encryption Keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• Customer-Managed Encryption Keys works with Eventarc From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Eventarc.”
• Customer-Managed Encryption Keys secures Eventarc From the official documentation: “You can [use customer-managed encryption keys (CMEK)](/eventarc/docs/use-cmek) to protect Eventarc.”
• Customer-Managed Encryption Keys secures Workflows From the official documentation: “[Use customer-managed encryption keys](/workflows/docs/use-cmek) so that your workflow and associated data at rest are protected using an encryption key that only you can access.”
• Eventarc is an alternative to Pub/Sub From the official documentation: “Instead of using Eventarc, you can use Pub/Sub to directly push messages to your service.”
• GKE works with Workflows From the official documentation: “Effective **May 2, 2025**, Workflows will not support [HTTP requests](/workflows/docs/http-requests) to the [IP-based endpoints](/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#ipendpointsconfig) of Google Kubernetes Engine (GKE) cluster control planes.”