service accounts

Related topics

• BigQuery Data Transfer Service works with service accounts From the official documentation: “Use service accounts with BigQuery Data Transfer Service”
• domain-wide authority configures service accounts From the official documentation: “Granting domain-wide authority lets the service account access your users' alerts by impersonating an administrator.”
• IAM roles configures service accounts From the official documentation: “This best practice lets you manage access by adding or removing IAM roles from the service account.”
• 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 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 Account Token Creator configures service accounts From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• service accounts is part of Identity and Access Management From the official documentation: “The Organization Policy Service provides constraints that can be used in [organization policies](/organization-policy/overview) to limit the usage of Identity and Access Management (IAM) [service accounts](/iam/docs/service-accounts).”
• service accounts is part of project From the official documentation: “Service accounts are owned by projects, and you can create many service accounts for a project.”
• service accounts depends on Storage Object Admin From the official documentation: “If you select a deletion option, the service account must have **Storage Object Admin** role instead of Storage Object Viewer.”
• 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up 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 secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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.”
• Storage Object Admin secures Cloud Storage From the official documentation: “**Storage Object Admin**: Write logs to GCS bucket and manage state files”
• service account key is an alternative to Workload Identity Federation From the official documentation: “For hosts outside of Google Cloud, you can provide a service account key or configure Workload Identity Federation (WIF).”
• service account keys is an alternative to Workload Identity Federation From the official documentation: “Where possible, consider using Workload Identity Federation instead of service account keys.”
• service account key is an alternative to Workload Identity Federation for GKE From the official documentation: “Enabling it lets you use IAM policies to grant Kubernetes workloads in your GKE cluster access to specific Google Cloud APIs without needing manual configuration or less secure methods like service account key files.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage 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.”
• 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 works with Workload Identity Federation for GKE From the official documentation: “Instead, your GKE cluster directly authenticates workloads using Google Cloud IAM.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, 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.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• service account key is part of service account From the official documentation: “A service account can have up to 10 keys.”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you are using the Google Cloud console, you can schedule recurring copies, and configure an email or Pub/Sub notifications with the BigQuery Data Transfer Service.”
• domain-wide authority configures service account From the official documentation: “To control API access for the service account using domain-wide delegation, do the following:”
• service account depends on Storage Object Admin From the official documentation: “If you select a deletion option, the service account must have **Storage Object Admin** role instead of Storage Object Viewer.”
• Application Default Credentials works with Workload Identity Federation From the official documentation: “ADC also supports [Workload Identity Federation](#workload-identity-federation), enabling applications to access Google Cloud resources from external platforms like Amazon Web Services (AWS), Microsoft Azure, or any identity provider that supports OpenID Connect (OIDC).”
• BigQuery Data Transfer Service works with Cloud Storage From the official documentation: “Retrieving events from the provided Pub/Sub subscription for Cloud Storage event-driven transfer”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• 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.”
• 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 depends on domain-wide authority From the official documentation: “After setting up domain wide delegation, [Application Default Credentials (ADC)](https://docs.cloud.google.com/docs/authentication/application-default-credentials) can be used for authentication.”
• 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…”
• 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 account From the official documentation: “BigQuery Data Transfer Service can use service account credentials for transfers with the following:”
• Cloud Storage is part of project From the official documentation: “All data in Cloud Storage belongs inside a project.”
• Cloud Storage works with Workload Identity Federation for GKE From the official documentation: “For example, consider a Kubernetes workload that uses Workload Identity Federation for GKE to store data in a Cloud Storage bucket.”
• domain-wide authority works with service account From the official documentation: “[Domain-wide delegation](https://support.google.com/a/answer/162106#zippy=%2Cset-up-domain-wide-delegation-for-a-client) enables a service account to impersonate any user in a Cloud Identity or Google Workspace account.”
• service account depends on 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 works with Workload Identity Federation From the official documentation: “[configure Workload Identity Federation](/iam/docs/workload-identity-federation-with-other-clouds) to let applications running on-premises or on other cloud providers use a service account.”
• service account works with Workload Identity Federation for GKE From the official documentation: “use [Workload Identity Federation for GKE](/kubernetes-engine/docs/how-to/workload-identity#authenticating_to) to attach service accounts to Kubernetes pods.”
• service account key secures Pub/Sub From the official documentation: “The Pub/Sub connection is authenticated using a service account key.”
• service account keys is an alternative to Workload Identity Federation for GKE From the official documentation: “Workload Identity Federation for GKE provides a simpler and safer alternative to using service account keys.”
• Storage Object Admin configures service account From the official documentation: “Grant the service account with **Storage Object Admin** role on the GCS bucket you created in the previous step.”
• Workload Identity Federation secures Cloud Storage From the official documentation: “To allow GKE to securely access the Cloud Storage bucket, set up GKE Workload Identity Federation:”
• Workload Identity Federation is part of Identity and Access Management From the official documentation: “[Identity and Access Management (IAM)](/iam/docs/overview) lets you manage fine-grained access to services and resources in Google Cloud. IAM includes features such as the following: - [Privileged Access Manager](/iam/docs/pam-overview), which manages on-demand, temporary…”
• Workload Identity Federation configures Pub/Sub From the official documentation: “If your architecture includes an [external identity provider](/iam/docs/workload-identity-federation#providers) such as Active Directory or a local Kubernetes cluster, you can use [workload identity federation](/iam/docs/workload-identity-federation) to manage access to Pub/Sub.”
• Workload Identity Federation for GKE secures Cloud Storage From the official documentation: “This command is required to grant the GKE service account permission to access the Cloud Storage bucket using Workload Identity Federation for GKE.”
• Workload Identity Federation for GKE is part of Workload Identity Federation From the official documentation: “[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity) is a GKE-specific implementation of Workload Identity Federation that provides a project-wide Google-managed *workload identity pool* from which applications running in GKE clusters get…”