Vertex AI

Related topics

• Cloud SQL works with Vertex AI From the official documentation: “[Integrate Cloud SQL with Vertex AI](/sql/docs/mysql/integrate-cloud-sql-with-vertex-ai)”
• embedding() works with Vertex AI From the official documentation: “The `embedding()` function in the `public` schema can be used with any Vertex AI embedding model without registering the endpoint.”
• BigQuery works with Vertex AI From the official documentation: “Token usage directly correlates with your Vertex AI billing for BigQuery generative AI functions that use Gemini models.”
• Identity and Access Management secures Vertex AI From the official documentation: “A Vertex AI model with an active endpoint that you have Identity and Access Management (IAM) permission to access.”
• AlloyDB works with Vertex AI From the official documentation: “Reference architecture for a RAG-capable generative AI application using Vertex AI and AlloyDB for PostgreSQL.”
• vector search works with Vertex AI From the official documentation: “Reference architecture for a RAG-capable generative AI application using Vertex AI and Vector Search.”
• Bigtable works with Vertex AI From the official documentation: “AssemblyAI builds complex speech-to-text models faster with Bigtable and Vertex AI.”
• Cloud Billing works with Vertex AI From the official documentation: “Cloud Billing bills overages for Gemini Enterprise and AI developer tools under Vertex AI API.”
• Dataflow works with Vertex AI From the official documentation: “Vertex AI models are subject to [Rate Limits and Quotas](https://cloud.google.com/vertex-ai/generative-ai/docs/quotas#view-the-quotas-by-region-and-by-model) and Dataflow automatically retries throttled requests with exponential backoff.”
• Google Cloud Storage works with Vertex AI From the official documentation: “Google Cloud's scalable and secure object storage service, recommended for storing large datasets used in training and verification with Vertex AI for optimal performance.”
• Semantic Search depends on Vertex AI From the official documentation: “The Vertex search option enables the Vertex AI-powered Semantic Search feature of API hub.”
• vector search is part of Vertex AI From the official documentation: “Vertex AI features for AutoML Forecasting, AutoML Tabular, Batch Prediction, Online Prediction, Pipelines, Training, Vector Search, and Vizier are available in [10 additional Google Cloud regions](/vertex-ai/docs/general/locations#feature-availability).”
• BigQuery works with Datastream From the official documentation: “Datastream supports three types of partitioning for BigQuery tables:”
• 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”
• 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 Billing From the official documentation: “[Export your Cloud Billing pricing data to BigQuery](/billing/docs/how-to/export-data-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.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
• 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 works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
• 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”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• 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).”
• Datastream works with Spanner From the official documentation: “Learn how Datastream ingests data from [Spanner](/datastream/docs/sources-spanner).”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Spanner From the official documentation: “Identity and Access Management (IAM) lets you control user and group access to Spanner resources at the project, Spanner instance, and Spanner database levels.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• 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.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud SQL works with Google Cloud Storage
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Compute Engine works with Google Cloud Storage From the official documentation: “The usage export bucket is a Google Cloud Storage bucket where Compute Engine usage reports are stored.”
• Google Cloud Storage works with Spanner From the official documentation: “- Export any Spanner database into a Cloud Storage bucket using either Avro or CSV file formats.”
• Identity and Access Management secures Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
• VPC Service Controls secures Compute Engine From the official documentation: “VPC Service Controls support for Compute Engine offers the following security benefits:”
• AlloyDB works with Compute Engine From the official documentation: “This page describes how to connect the `psql` client tool from Compute Engine to an AlloyDB instance.”
• 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.”
• Bigtable works with Cloud Storage From the official documentation: “For example, if you frequently write data to Bigtable from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your Bigtable cluster in a zone within `us-central1`.”
• Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
• Bigtable works with Compute Engine From the official documentation: “The Compute Engine instances can connect to and manage the Bigtable instance.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Dataflow From the official documentation: “Information stored in [Cloud Logging](/logging/docs/region-support) is primarily generated by the code in your Dataflow program.”