Diagram

A sequence diagram with three lifelines: the caller workload, the Service Account Credentials API, and the target Google Cloud API. Animated arrows show the caller requesting a short-lived token, the API signing it with the escrowed Google-owned key, the token returning to the caller with a 1-hour default expiry, and the caller presenting the token to the Google Cloud API.
How Short-Lived Credentials Are Created
How short-lived credentials are created depends on a trusted identity asking the Service Account Credentials API to mint them on demand. In many cases the credentials are obtained automatically, so no key file has to be distributed. The flow always runs from the API to the requesting workload, and the workload then presents the credential to Google Cloud APIs:
--impersonate-service-account flag creates short-lived credentials for that service account and runs the command with them.Domain 6 of 7
24 practice questions
Practice this DomainLast updated