service account impersonation

Related topics

• Workload Identity depends on service account impersonation From the official documentation: “Workload Identity is the recommended approach as it uses short-lived access tokens using service account impersonation.”
• Application Default Credentials works with service account impersonation From the official documentation: “You can use service account impersonation to set up a local Application Default Credentials (ADC) file.”
• Google Cloud CLI works with service account impersonation From the official documentation: “The gcloud CLI provides a straightforward way to use service account impersonation.”
• service account impersonation configures Application Default Credentials From the official documentation: “You can use service account impersonation to set up a local ADC file.”
• service account impersonation depends on Service Account Token Creator From the official documentation: “You must have the Service Account Token Creator (`roles/iam.serviceAccountTokenCreator`) IAM role on the service account you are impersonating.”
• Application Default Credentials depends on service account impersonation From the official documentation: “For Looker connections to Cloud SQL that use ADC, ADC [impersonates](/iam/docs/service-account-impersonation) a service account or a chain of service accounts to access your database.”
• Connect gateway works with service account impersonation From the official documentation: “The Connect gateway supports [service account impersonation](/iam/docs/service-account-impersonation), so even if you're logged in to your own user account you can use a service account to interact with clusters, as you'll see in the following sections.”
• Google Cloud CLI configures service account impersonation From the official documentation: “You can also use service account impersonation by configuring your `gcloud config` before running the tool.”
• service account works with service account impersonation From the official documentation: “While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account.”
• service account impersonation is part of Google Cloud CLI From the official documentation: “You can also use service account impersonation by configuring your `gcloud config` before running the tool.”
• service account impersonation depends on Service Account Credentials API From the official documentation: “To impersonate a service account, you need to enable the Service Account Credentials API in your project.”
• service account impersonation is an alternative to service account keys From the official documentation: “If you use impersonation, instead of creating service account keys that anyone can use to access your deployment, you manage access by granting or revoking the [Service Account Token Creator (`roles/iam.serviceAccountTokenCreator`) IAM…”
• Service Account Token Creator configures service account impersonation From the official documentation: “To run the export utility script locally, your user account must have permission to impersonate the service account. Grant your user account the **Service Account Token Creator** role (`roles/iam.serviceAccountTokenCreator`) on the service account.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Service Account Token Creator configures service account From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• 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.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• 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 Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Build works with Connect gateway From the official documentation: “Learn how to [access Anthos clusters from Cloud Build with the connect gateway](/../anthos/multicluster-management/gateway/tutorials/cloud-build-integration).”
• 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.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• 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 Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• 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.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with Google Cloud CLI From the official documentation: “To do so, provide your user credentials to ADC by using the Google Cloud CLI.”
• 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 service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Google Cloud CLI depends on Application Default Credentials From the official documentation: “To authenticate with the gcloud CLI, generate a local Application Default Credentials (ADC) file by running this command.”
• Google Cloud CLI works with Spanner From the official documentation: “You have already set up [gcloud CLI](/sdk/docs) for use with Spanner.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with Workload Identity From the official documentation: “Using [Workload Identity](/kubernetes-engine/docs/how-to/workload-identity) is the recommended way to allow GKE workloads to authenticate with Google APIs and for administrators to apply "least privilege" authorization controls using IAM.”
• service account keys is part of service account From the official documentation: “You use the Identity and Access Management API to create a new key pair for a service account.”
• Workload Identity depends on service account From the official documentation: “Workload Identity is the recommended approach because it uses short-lived tokens by using service account impersonation.”
• Workload Identity configures service account From the official documentation: “Workload Identity binds a KSA to a GSA, causing any deployments with that KSA to authenticate as the GSA in their interactions with Google Cloud.”
• Application Default Credentials works with Cloud Build From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials is an alternative to Google Cloud CLI From the official documentation: “You can authenticate to [the Vision API](/vision/docs/reference/rest) by using your [gcloud CLI credentials](/sdk/docs/authenticate) or by using [Application Default Credentials](/docs/authentication/application-default-credentials).”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Application Default Credentials is an alternative to service account keys From the official documentation: “When developers are locally iterating on Terraform configuration, they should authenticate by running [`gcloud auth application-default login`](https://cloud.google.com/sdk/gcloud/reference/auth/application-default/login) to generate application default credentials. Don't…”
• Cloud Build depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build works with Compute Engine From the official documentation: “Automating builds on repository events ensures that Cloud Build immediately validates, builds, and publishes your custom OS images to Compute Engine and Artifact Registry upon code review or merge.”