service account

Related topics

• Eventarc trigger depends on service account From the official documentation: “Eventarc triggers are linked to service accounts to use as an identity when invoking your function.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• service account works with Vertex AI From the official documentation: “The service account can interact with Vertex AI services.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Cloud Scheduler depends on service account From the official documentation: “To sync a replicated taxonomy across locations with Cloud Scheduler, you need a service account.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• Vertex AI depends on service account From the official documentation: “To use the Google Vertex AI model endpoints, you must add Vertex AI permissions to the service account that you used while installing AlloyDB Omni.”
• Cloud Key Management Service works with service account From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• Cloud resource connection depends on service account 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 resource connection works with service account From the official documentation: “When you create a connection resource, BigQuery creates a unique system service account and associates it with the connection.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• IAM roles configures service account From the official documentation: “2. [Grant the necessary Identity and Access Management roles](#grant-iam-roles) to your service account.”
• scheduled query works with service account From the official documentation: “This service account will be used to execute the scheduled queries.”
• service account is part of Cloud resource connection From the official documentation: “When you create a connection resource, BigQuery creates a unique system service account and associates it with the connection.”
• Workflows depends on service account From the official documentation: “You need a service account for Workflows (to run the pipeline) and for Managed Service for Apache Spark (to run the connector).”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• IAM roles works with service account From the official documentation: “In this section, you designate the service account for the gateway proxies and assign them the correct IAM roles.”
• Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”
• service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
• service account depends on Cloud Key Management Service From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• service account secures Cloud SQL From the official documentation: “Cloud SQL uses service accounts for authentication between Cloud SQL and other Google Cloud products.”
• service account depends on Google Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket. You must grant this service account access to your bucket.”
• service account configures scheduled query From the official documentation: “If you configure the scheduled query to use a service account, it runs using the service account's credentials.”
• service account works with Spanner From the official documentation: “The service account has access to the Spanner instance.”
• 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 works with Cloud Scheduler From the official documentation: “Create a Cloud Scheduler job that triggers the Cloud Run service daily.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• 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: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• Cloud Run works with Cloud SQL From the official documentation: “Connecting from Cloud Run (fully managed) to Cloud SQL”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Cloud Run works with Eventarc trigger From the official documentation: “You can create a trigger for a Cloud Run destination using Terraform.”
• Cloud Scheduler works with Workflows From the official documentation: “[Schedule a workflow using Cloud Scheduler](/workflows/docs/schedule-workflow)”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Eventarc trigger works with Workflows From the official documentation: “# Create an Eventarc trigger that routes Cloud Storage events to Workflows”
• Cloud Run works with Google Cloud Storage From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket.”
• Cloud SQL works with Vertex AI From the official documentation: “This page describes how to integrate Cloud SQL with [Vertex AI](/vertex-ai/docs).”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Cloud Storage works with Eventarc trigger From the official documentation: “# Create an Eventarc trigger, routing Cloud Storage events to Workflows”
• Eventarc trigger works with GKE From the official documentation: “You can create a trigger for a GKE destination using Terraform.”
• BigQuery works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• BigQuery works with Vertex AI From the official documentation: “The page provides guidance for getting predictions from Vertex AI, based on retail [data exported into BigQuery](/retail/docs/export-data-into-bq).”
• 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 is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• 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 Run works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• IAM roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
• 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.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• 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.”