Service Account Token Creator

Related topics

• Service Account Token Creator configures service account From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• 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.”
• service account depends on Service Account Token Creator From the official documentation: “Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the next service account in the list.”
• Service Account Token Creator secures service account From the official documentation: “Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the next service account in the list.”
• 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.”
• Service Account Token Creator configures service accounts From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• Service Account Token Creator secures user-managed service account From the official documentation: “- **User-managed execution identity**: Enrichment tasks run using a user-managed service account, which is an identity you create and manage in your project to allow services to act on your behalf. The Dataplex Service Agent (P4SA) impersonates this service account by using the…”
• service agent depends on Service Account Token Creator From the official documentation: “To enable the service agent to generate an [access token](/docs/authentication/token-types#access-tokens) from the user-managed service account, grant the service agent access to the user-managed service account, and assign the **Service Account Token Creator** role…”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, 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.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• 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.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• 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 From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• 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.”
• BigQuery Data Transfer Service works with service account From the official documentation: “BigQuery Data Transfer Service lets you authenticate data transfers for supported data sources by using a [service account](/iam/docs/service-account-overview) instead of individual user credentials.”
• BigQuery Data Transfer Service depends on service agent From the official documentation: “The BigQuery Data Transfer Service uses a [service agent](/iam/docs/service-account-types#service-agents) to access and manage your resources.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Compute Engine works with user-managed service account From the official documentation: “A user-managed service account can be attached to a Compute Engine instance to provide credentials to applications running on the instance.”
• 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 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 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 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 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.”
• 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…”
• BigQuery Data Transfer Service works with service accounts From the official documentation: “Use service accounts with BigQuery Data Transfer Service”
• BigQuery Data Transfer Service configures service agent From the official documentation: “When you enable the BigQuery Data Transfer Service API, a [service agent](/bigquery/docs/enable-transfer-service#service_agent) is created for your project.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Cloud Run works with user-managed service account From the official documentation: “You can also configure a user-managed service account for Cloud Run.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• 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 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 keys depends on service accounts From the official documentation: “A [service account key](/iam/docs/service-account-overview) lets you authenticate a request as a service account.”
• service agent depends on service account From the official documentation: “The BigQuery Data Transfer Service uses a [*service agent*](/iam/docs/service-account-types#service-agents) to get the access token for the user-provided service account (transfer owner).”
• service agent is an alternative to user-managed service account From the official documentation: “Grant the permissions listed in [Service agent permissions](/storage-transfer/docs/iam-cloud#manually_assigning_roles) to the user-managed service account, instead of to the service agent.”