Cloud Asset Inventory

Related topics

• BigQuery works with Cloud Asset Inventory From the official documentation: “You can also use Cloud Asset Inventory to transfer this data into BigQuery.”
• Cloud Asset Inventory depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Asset Inventory From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Asset Inventory From the official documentation: “To authenticate to Cloud Asset Inventory, set up Application Default Credentials.”
• Cloud Asset Inventory works with Cloud Storage From the official documentation: “To analyze changes, export your asset metadata to BigQuery or Cloud Storage.”
• Cloud Asset Inventory works with Pub/Sub From the official documentation: “Treat Cloud Asset Inventory Pub/Sub feeds as informative signals.”
• Cloud Asset Inventory works with Secret Manager From the official documentation: “The integration between Secret Manager and Cloud Asset Inventory helps you do the following:”
• Cloud Asset Inventory works with VPC Service Controls From the official documentation: “VPC Service Controls can be used with Cloud Asset Inventory to provide additional security for your assets.”
• allow policy works with Cloud Asset Inventory From the official documentation: “Only [allow policies](/iam/docs/policies) are supported for retrieval through Cloud Asset Inventory.”
• Cloud Asset Inventory works with Cloud KMS From the official documentation: “You can use Cloud Asset Inventory to programmatically list and filter your Cloud KMS assets by algorithm type.”
• Cloud Asset Inventory works with Cloud KMS Autokey From the official documentation: “You can use a SQL query with Cloud Asset Inventory to evaluate the effective Autokey configuration for all projects within a folder or an organization.”
• Cloud Asset Inventory works with Cloud Logging From the official documentation: “When real-time feeds fail to send resources or IAM policy updates through Pub/Sub, Cloud Asset Inventory logs the error status and message in Logging.”
• Cloud Asset Inventory works with gcloud CLI From the official documentation: “You can use the Google Cloud CLI and Cloud Asset Inventory to search for resources that might block organization deletion.”
• Cloud Asset Inventory works with Policy Analyzer From the official documentation: “You can use Cloud Asset Inventory as part of [Policy Analyzer](/policy-intelligence/docs/policy-analyzer-overview) to view the following policies on resources:”
• Identity and Access Management secures Cloud Asset Inventory From the official documentation: “Cloud Asset Inventory uses [Identity and Access Management](/iam/docs) (IAM) for access control.”
• Policy Analyzer is part of Cloud Asset Inventory From the official documentation: “You can use the [Policy Analyzer feature](/policy-intelligence/docs/analyze-iam-policies#principal-query-all) in the Cloud Asset Inventory to find all users with any of the permissions included in the **Gemini for Google Cloud User** role and the **Service Usage Consumer** role.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• 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 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.”
• 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.”
• customer-managed encryption keys depends on Cloud KMS From the official documentation: “You must have a symmetric encryption key in Cloud KMS to use for CMEK.”
• Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
• Application Default Credentials works with Cloud KMS From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Cloud Run works with Secret Manager From the official documentation: “You can integrate Secret Manager with other Google Cloud products such as Cloud Run.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• 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 KMS depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
• 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.”
• 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 Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• 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 Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• customer-managed encryption keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”