short-lived credentials

Related topics

• Service Account Credentials API works with short-lived credentials From the official documentation: “[Create short-lived credentials](/iam/docs/create-short-lived-credentials-direct) using the Service Account Credentials API, then use those credentials to authenticate an API request.”
• service account key is an alternative to short-lived credentials From the official documentation: “Short-lived service account credentials are useful for scenarios where you need to grant limited access to resources for trusted service accounts, and they reduce the risk compared to using long-lived credentials like service account keys.”
• service account keys is an alternative to short-lived credentials From the official documentation: “Applications can obtain short-lived credentials or, less securely, use service account keys to authenticate.”
• 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 From the official documentation: “Workload Identity Federation lets you access Google Cloud resources from outside of Google Cloud without using a service account key.”
• service account works with Workload Identity Federation From the official documentation: “When an application uses Workload Identity Federation, it impersonates a service account.”
• service account key is part of service account From the official documentation: “Create a service account key:”
• service account key is an alternative to Workload Identity Federation for GKE From the official documentation: “[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity) is the recommended way for mesh workloads to securely access Google services. The alternative of storing a [service account key](/iam/docs/creating-managing-service-account-keys) in a…”
• 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.”
• 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.”
• 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 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 is an alternative to Workload Identity Federation for GKE From the official documentation: “If you do not enable Workload Identity Federation for GKE, you need to register the cluster with a Google Cloud service account for authentication, and complete the additional steps in [Authenticating service accounts](#authenticating).”
• 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 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 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.”
• service accounts works with Workload Identity Federation for GKE From the official documentation: “Config Connector creates and manages Google Cloud resources by authenticating with an Identity and Access Management (IAM) service account and using Workload Identity Federation for GKE to bind IAM service accounts with Kubernetes service accounts.”
• 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…”