data lineage

Related topics

• BigQuery works with data lineage From the official documentation: “Use data lineage to identify unused assets and optimize costs in your BigQuery project.”
• Cloud Storage works with data lineage From the official documentation: “Data lineage is available for all Managed Service for Apache Spark jobs except SparkR and Spark streaming jobs, and supports BigQuery and Cloud Storage data sources.”
• data lineage depends on Application Default Credentials From the official documentation: “To authenticate to Data Lineage, set up Application Default Credentials.”
• data lineage is part of Knowledge Catalog From the official documentation: “About data lineage visualization in Knowledge Catalog”
• data lineage works with Model Context Protocol From the official documentation: “This page explains how to connect data lineage to developer tools such as the Gemini CLI and other Model Context Protocol (MCP) clients.”
• VPC Service Controls secures data lineage From the official documentation: “Data lineage as part of Knowledge Catalog offers VPC-SC support.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Sensitive Data Protection depends on Application Default Credentials From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery works with Sensitive Data Protection From the official documentation: “Uses the Data Loss Prevention API to analyze BigQuery data.”
• 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”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• Application Default Credentials secures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Data Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Data Catalog, set up Application Default Credentials.”
• Application Default Credentials works with Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
• 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 Gemini Enterprise Agent Platform From the official documentation: “The BigQuery dataset stores all versions for the associated Gemini Enterprise Agent Platform dataset.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Application Default Credentials secures Gemini Enterprise Agent Platform From the official documentation: “To authenticate to Agent Platform, set up Application Default Credentials.”
• Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• 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).”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Application Default Credentials works with Data Catalog From the official documentation: “To authenticate to Data Catalog, set up Application Default Credentials.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Application Default Credentials works with Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• 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 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.”
• Data Catalog is an alternative to Knowledge Catalog From the official documentation: “Use Knowledge Catalog for all new projects to take advantage of AI-powered features and enhanced governance.”
• 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.”
• 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.”
• Data Catalog is part of Knowledge Catalog From the official documentation: “Knowledge Catalog features”
• VPC Service Controls secures Cloud SQL From the official documentation: “VPC Service Controls perimeters protect the Cloud SQL Admin API.”
• 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.”
• Application Default Credentials works with Gemini Enterprise Agent Platform From the official documentation: “To authenticate to Agent Platform, set up Application Default Credentials.”
• Application Default Credentials configures Sensitive Data Protection From the official documentation: “To authenticate to Sensitive Data Protection, set up Application Default Credentials.”
• BigQuery works with Data Catalog From the official documentation: “The instructions in this page use both BigQuery and Data Catalog.”
• 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.”
• Data Catalog works with Sensitive Data Protection From the official documentation: “Send job results to Data Catalog. This feature is [deprecated](/sensitive-data-protection/docs/deprecations).”
• Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• 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 Knowledge Catalog From the official documentation: “IAM controls access to your Knowledge Catalog resources at the Google Cloud resource level.”
• 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.”
• Knowledge Catalog works with Sensitive Data Protection From the official documentation: “Send the results of a [BigQuery inspection job](/sensitive-data-protection/docs/inspecting-storage#inspect_a_table) to Knowledge Catalog.”
• Sensitive Data Protection works with VPC Service Controls From the official documentation: “For information about VPC Service Controls support for Sensitive Data Protection, see the [Supported products](/vpc-service-controls/docs/supported-products#table_dlp) table in the VPC Service Controls documentation.”
• VPC Service Controls secures Knowledge Catalog From the official documentation: “The API for Knowledge Catalog can be protected by VPC Service Controls and the product can be used normally inside service perimeters.”