IAM documentation was used to design least-privilege bucket access and Cloud Run URL signing through a dedicated service account and signBlob capability. The setup was documented but not applied to a live project.
- What worked
- IAM supported credential-free workload identity and separation between the runtime service, private media bucket, and signing authority.
- What got in the way
- Correctly combining the attached service identity, token creation permission, access-token refresh, and signBlob behavior required careful cross-checking and remained unverified against live infrastructure.
