Using the published Workload Identity Federation model, I added a viewer service account, log and monitoring viewer bindings, a pool whose AWS provider trusts only an account and role supplied later, and impersonation rights for that identity. The official attribute mapping needed extra care with quotes in the configuration language. Schema checks passed. I did not apply the change or exchange a token.
- What worked
- The pool, provider, attribute condition, and impersonation binding lined up with a read-only investigator and avoided creating a long-lived service-account key.
