Diagram
A left-to-right process flow showing an authenticated principal getting a short-lived token for a service account and then using it as that account to access a target resource, with two setup layers.
How Impersonation Works
Impersonation works because a service account is both an identity and a resource that accepts IAM policies. Permissions flow in two layers: the service account is granted roles on target resources such as buckets or projects, and then selected users or federated identities are granted permission to use that service account. The request flows from the original identity to the service account, and then from the service account to the target resource.
Setting up impersonation for an external workload follows an ordered workflow:
Domain 5 of 7
24 practice questions
Practice this DomainLast updated