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.”
• push subscription depends on Service Account Token Creator From the official documentation: “To use Pub/Sub with authentication, create another subscription: ```bash # Configure the push subscription gcloud pubsub subscriptions create YOUR_SUBSCRIPTION_NAME \ --topic=YOUR_TOPIC_NAME \ --push-auth-service-account=YOUR-SERVICE-ACCOUNT-EMAIL\…”
• 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 configures Compute Engine default service account From the official documentation: “Grant the following Identity and Access Management (IAM) roles to the [Compute Engine default service account](/compute/docs/access/service-accounts#default_service_account): - **Managed Kafka Client** (`roles/managedkafka.client`) - **Schema Registry Admin**…”
• 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 Subscription From the official documentation: “To use Pub/Sub with authentication, create another subscription: ```bash # Configure the push subscription gcloud pubsub subscriptions create YOUR_SUBSCRIPTION_NAME \ --topic=YOUR_TOPIC_NAME \ --push-auth-service-account=YOUR-SERVICE-ACCOUNT-EMAIL\…”
• 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…”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• 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 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 Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• service account key is part of service account From the official documentation: “Create a service account key:”
• Cloud Run depends on Compute Engine default service account From the official documentation: “By default, Cloud Run uses the [Compute Engine default service account](/compute/docs/access/service-accounts#default_service_account).”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you intend to set up transfer run notifications for Pub/Sub, you must have `pubsub.topics.setIamPolicy` permissions.”
• 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 works with Compute Engine default service account From the official documentation: “By default, Cloud Run runs your notifier images with the **Compute Engine default service account** and uses it to fetch your secret.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud Run works with push subscription From the official documentation: “You can use a Pub/Sub push subscription to push messages to a Cloud Run service.”
• Cloud Run functions 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.”
• 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.”
• Compute Engine default service account is an alternative to service account From the official documentation: “Instead of the Compute Engine default service account, create and use a less privileged service account for your nodes.”
• Compute Engine default service account is an alternative to user-managed service account From the official documentation: “You can either create a user-managed service account or use the Compute Engine default service account.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• push subscription is part of Pub/Sub From the official documentation: “Creates a Pub/Sub push subscription.”
• service account works with service account key From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• service account impersonation is an alternative to service account key From the official documentation: “If you cannot use a user account or service account impersonation for local development, you can use a service account key.”
• Subscription is part of Pub/Sub From the official documentation: “This document discusses how to delete subscriptions in Pub/Sub.”
• BigQuery Data Transfer Service depends on Pub/Sub From the official documentation: “The communication channel between the agent running on premises and BigQuery Data Transfer Service is by publishing Pub/Sub messages to a per transfer topic.”
• 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 is an alternative to Cloud Run functions From the official documentation: “The blueprint supports the following use cases: - Deploying a serverless architecture using Cloud Run functions (this document) - [Deploying a serverless architecture using Cloud Run](/architecture/blueprints/serverless-blueprint)”
• 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.”
• Cloud Run functions is part of Cloud Run From the official documentation: “| Cloud Run functions | Standalone functions on Cloud Run. |”
• Cloud Run functions is an alternative to Compute Engine From the official documentation: “Cloud Run functions and App Engine don't offer a two-way configurable firewall, so you must either create compensating controls or deploy the tokenization service on Compute Engine or Google Kubernetes Engine.”
• Cloud Run functions depends on service accounts From the official documentation: “Your Cloud Run function runs as an automatically created service account.”
• Cloud Run functions works with user-managed service account From the official documentation: “Some Google Cloud services—such as Compute Engine, App Engine, and Cloud Run functions—support attaching a [user-managed service account](/iam/docs/service-account-types#user-created) to some types of resources.”
• Compute Engine depends on Compute Engine default service account From the official documentation: “Each Compute Engine app uses an [Compute Engine default service account](/compute/docs/access/service-accounts#default_service_account) to manage access to Google Cloud services such as Firestore.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• Compute Engine default service account is part of user-managed service account From the official documentation: “User-managed service accounts include new service accounts that you explicitly create and the Compute Engine default service account.”
• Pub/Sub depends on Cloud Run functions From the official documentation: “After you have set up Cloud Run functions to process model output and generate events, you can set up event notification with Pub/Sub.”
• push subscription is part of Subscription From the official documentation: “Pub/Sub offers standard subscriptions such as *push* and *pull* subscriptions.”
• 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 key secures Pub/Sub From the official documentation: “The Pub/Sub connection is authenticated using a service account key.”
• service account key is part of service accounts From the official documentation: “Managing service identities involves both the service identity (represented by a `ProjectServiceAccount` resource) and its associated credentials (public and private key pairs).”
• service agent depends on Pub/Sub From the official documentation: “Your service agent must have [publishing access](/pubsub/docs/access-control#console) on the Pub/Sub topic.”
• 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.”