BigQuery connection

Related topics

• BigQuery connection is part of BigQuery From the official documentation: “In Cloud Shell, create a BigQuery connection to access Cloud Run:”
• BigQuery connection works with BigQuery dataset From the official documentation: “Ensure that the BigQuery connection and the BigQuery dataset exist in the same region, and that they are compatible with the location of the Cloud Storage bucket.”
• BigQuery connection works with Cloud Run From the official documentation: “In Cloud Shell, create a BigQuery connection to access Cloud Run:”
• BigQuery connection works with Cloud Storage From the official documentation: “Grant the service account for the BigQuery connection an IAM role that lets it read data stored in your Cloud Storage bucket:”
• BigQuery connection works with Cloud Storage bucket From the official documentation: “Ensure that the BigQuery connection and the BigQuery dataset exist in the same region, and that they are compatible with the location of the Cloud Storage bucket.”
• BigQuery Connection API configures BigQuery connection From the official documentation: “The BigQuery connection API lets you manage BigQuery connections to external data sources such as a Spanner database.”
• IAM policy secures BigQuery connection From the official documentation: “The policy defines which principals have what permissions on the connection resource.”
• remote model depends on BigQuery connection From the official documentation: “REMOTE WITH CONNECTION {DEFAULT | `PROJECT_ID.REGION.CONNECTION_ID`}”
• 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.”
• CMEK secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• 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”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• BigQuery dataset is part of BigQuery From the official documentation: “Sample demonstrating how to create a dataset in BigQuery.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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.”
• CMEK secures BigQuery From the official documentation: “Enable CMEK for BigQuery Tables”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• CMEK secures Cloud Storage From the official documentation: “Enable CMEK for Cloud Storage Buckets”
• 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”
• 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 resource connection works with Cloud Storage From the official documentation: “Cloud resource connection lets BigQuery access Cloud Storage object data and metadata using its own service account.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• BigQuery works with Cloud resource connection From the official documentation: “After you create the training dataset, you establish a connection to link BigQuery and external sources.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• BigQuery dataset works with Cloud resource connection From the official documentation: “Create the connection in the same [location](/bigquery/docs/locations) as the dataset you created in the previous step.”
• Cloud resource connection is part of BigQuery From the official documentation: “A Cloud resource connection in BigQuery lets you connect BigQuery to other Google Cloud services and external storage by using a dedicated service account with delegated access.”
• 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).)”
• BigQuery depends on BigQuery Connection API From the official documentation: “To create remote connections in BigQuery for Gemini and embeddings models, enable the BigQuery Connection API in your Google Cloud project.”
• BigQuery depends on Cloud resource connection From the official documentation: “BigQuery uses a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) to interact with the Cloud AI service.”
• 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 Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
• BigQuery works with remote model From the official documentation: “The function uses a BigQuery ML [remote model](/bigquery/docs/reference/standard-sql/bigqueryml-syntax-create-remote-model-service) to connect BigQuery to the Cloud Natural Language API.”
• BigQuery dataset works with Cloud Run From the official documentation: “The Cloud Run service can interact with the BigQuery dataset.”
• BigQuery dataset works with Cloud Storage bucket From the official documentation: “When you query data in Cloud Storage by using a [BigLake](/bigquery/docs/query-cloud-storage-using-biglake) or a [non-BigLake external table](/bigquery/docs/query-cloud-storage-data), the bucket must be colocated with your BigQuery dataset that contains the external table…”
• BigQuery dataset works with Pub/Sub From the official documentation: “The Pub/Sub subscription can write messages to the BigQuery dataset.”
• Cloud resource connection depends on BigQuery Connection API From the official documentation: “These external connections use the BigQuery Connection API.”
• Cloud resource connection depends on Cloud Storage From the official documentation: “- `CONNECTION_ID`: A `STRING` value that contains a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) that the service can use to access the objects in Cloud Storage, in the format `location.connection_id`.”
• Cloud resource connection works with remote model From the official documentation: “Create a [Cloud resource connection](/bigquery/docs/create-cloud-resource-connection) for the remote model to use, and get the connection's service account.”
• 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 SQL works with Cloud Storage bucket From the official documentation: “If you exported into a Cloud Storage bucket, you can also check the log file created by Cloud SQL in the bucket for information about export status.”
• 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 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).”
• CMEK secures Cloud Run From the official documentation: “You use the CMEK keys to help protect your data in Artifact Registry and in Cloud Run.”
• CMEK secures Cloud Storage bucket From the official documentation: “You can [manually encrypt](/storage/docs/encryption/using-customer-managed-keys) the environment's bucket with CMEK keys before you create an environment.”
• CMEK works with Pub/Sub From the official documentation: “By using Pub/Sub with CMEK, you are able to meet locality rules about encryption while still maintaining high availability.”
• 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.”