dataset

Related topics

• dataset is part of BigQuery From the official documentation: “To create a BigQuery dataset, select one of the following options:”
• customer-managed encryption keys secures dataset From the official documentation: “If you have specific compliance or regulatory requirements related to the keys that protect your data, create your dataset using the instructions in [Enable customer-managed encryption keys (CMEK) for Cloud Healthcare API datasets](/healthcare-api/docs/cmek).”
• dataset is part of Agent Platform From the official documentation: “This page shows you how to create an Agent Platform dataset from your image data so you can start training classification models.”
• dataset is part of Gemini Enterprise Agent Platform From the official documentation: “This resource always executes the training task, and optionally may also export data from a Gemini Enterprise Agent Platform `Dataset` which becomes the training input, upload the Model to Gemini Enterprise Agent Platform, and evaluate the Model.”
• dataset depends on Google Cloud Storage From the official documentation: “Create a dataset using an empty Cloud Storage bucket.”
• dataset works with TrainingPipeline From the official documentation: “The AutoML `TrainingPipeline` resource orchestrates tasks associated with training an AutoML model. This resource always executes the training task, and optionally may also export data from a Gemini Enterprise Agent Platform `Dataset` which becomes the training input, upload…”
• Identity and Access Management secures dataset From the official documentation: “IAM lets you control who has access to your datasets and data stores.”
• 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”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• 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 Run functions works with Cloud Storage From the official documentation: “Set up functions in response to events in Cloud Storage:”
• BigQuery works with Cloud Run functions From the official documentation: “BigQuery supports external function calls through Cloud Run functions.”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• 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.”
• 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.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• 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”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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 works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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.”
• customer-managed encryption keys secures Gemini Enterprise Agent Platform From the official documentation: “Enable customer-managed encryption keys (CMEK) for the Gemini Enterprise Agent Platform to gain more control over data encryption and key management.”
• 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 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.”
• 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.”
• AlloyDB for PostgreSQL works with BigQuery From the official documentation: “BigQuery AlloyDB federation lets BigQuery query data residing in AlloyDB in real time without copying or moving the data.”
• AlloyDB for PostgreSQL works with Cloud Storage From the official documentation: “AlloyDB supports importing and exporting compressed `.gz` files from Cloud Storage.”
• AlloyDB for PostgreSQL works with Gemini Enterprise Agent Platform From the official documentation: “Integrate AlloyDB with Gemini Enterprise Agent Platform”
• 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.”
• Cloud Run functions works with Google Cloud Storage From the official documentation: “Service account for Dataminr Alerts Cloud Run function to write alert data to GCS”
• 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.”
• Agent Platform works with Cloud Storage From the official documentation: “Load the model's `state_dict` object into Cloud Storage by using a Agent Platform custom job:”
• AlloyDB for PostgreSQL works with Pub/Sub From the official documentation: “Although AlloyDB doesn't provide a built-in method for automating exports, you can build an automation tool using other Google Cloud components such as Cloud Scheduler, Pub/Sub, and Cloud Run functions.”
• Cloud Logging works with Cloud Run functions From the official documentation: “Cloud Run functions is configured to use Cloud Logging automatically.”
• Cloud Logging is an alternative to Google Cloud Storage From the official documentation: “When you specify your own service account for builds, you must store your build logs in a Cloud Logging bucket, in a user-created Cloud Storage bucket, or in a Google Cloud-created and user-owned Cloud Storage bucket.”
• Cloud Run functions depends on Cloud Storage From the official documentation: “Cloud Run functions uses the config in Cloud Storage to determine what actions to take for each stateful MIG.”
• Cloud Storage works with Gemini Enterprise Agent Platform From the official documentation: “This page describes how to use Gemini Enterprise Agent Platform to export your image AutoML Edge models to Cloud Storage.”
• customer-managed encryption keys secures Cloud Logging From the official documentation: “Cloud Logging supports encrypting Log storage with CMEK keys.”
• 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.”
• Identity and Access Management secures Gemini Enterprise Agent Platform From the official documentation: “Agent Platform uses IAM to manage access to resources.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• 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 Google Cloud Storage From the official documentation: “Storage Transfer Service supports on-premises transfers to Cloud Storage buckets protected by VPC Service Controls, under the following conditions:”
• Agent Platform works with AlloyDB for PostgreSQL From the official documentation: “To enable AlloyDB to use Agent Platform text embedding models, you must add Agent Platform user permissions to the AlloyDB service agent for the project where your cluster and instance is located.”
• Agent Platform works with BigQuery From the official documentation: “BigQuery and Agent Platform are tightly integrated, letting you access and analyze your data directly within the Agent Platform platform.”
• Agent Platform works with Cloud Logging From the official documentation: “If any containers restart before Agent Platform shuts down the entire job, these containers may produce logs in Cloud Logging.”
• Agent Platform works with Cloud Run functions From the official documentation: “Cloud Run functions can serve predictions from your Agent Platform models, letting you create an API endpoint for your model without having to manage any infrastructure.”
• Agent Platform works with Pub/Sub From the official documentation: “Pub/Sub enables event-driven communication so that you can trigger Agent Platform pipelines based on events that are published to Pub/Sub topics.”
• Agent Platform works with VPC Service Controls From the official documentation: “If you use Agent Platform in a VPC-SC environment, you must create an ingress rule in your perimeter to allow ingress from the Reasoning Engine Service Agent (`service-PROJECT_NUMBER@gcp-sa-aiplatform-re.iam.gserviceaccount.com`) into the `storage.googleapis.com` service and…”
• AlloyDB for PostgreSQL works with Cloud Logging From the official documentation: “AlloyDB processes user-generated audit logs asynchronously before securely forwarding them to Cloud Logging.”