Featured
Swap service account keys in GitHub secrets for short-lived OIDC tokens, lock the trust to your own repo, and deploy to Cloud Run with no JSON key.
11 min
Topic 02 / 08 · 07 articles
About this topic
130 words
Identity and access management is the part of cloud engineering that is invisible when it is right and catastrophic when it is wrong. A single over-broad role or a service-account key sitting in a CI secret is often all an attacker needs.
This topic collects practical guides for getting Google Cloud IAM right without drowning in policy documents: granting access to groups instead of people, giving every workload its own service account, replacing downloaded keys with Workload Identity Federation, scoping Secret Manager access to individual secrets, and verifying tokens once at the edge instead of in every service.
Every guide includes the exact gcloud commands or configuration I use, the mistakes I have seen in real projects, and a checklist you can run against your own organisation in an afternoon.
Featured
Swap service account keys in GitHub secrets for short-lived OIDC tokens, lock the trust to your own repo, and deploy to Cloud Run with no JSON key.
11 min
· 9 min
Most small teams should not start with a service perimeter. The organization prerequisite, the friction it adds, and when it pays for itself.
9 min
· 11 min
A Firestore rules deploy replaces everything at once, with no canary. The traps in the rules and the release path, and the pipeline that catches them.
11 min
· 9 min
An Eventarc trigger delivering to a private Cloud Run service passes four identity checks. A 401/403 reference table, and the setup that keeps each one correct.
9 min
· 13 min
A one-hour audit procedure for Google Cloud IAM: snapshot the policies, run eight targeted queries, triage what you find, and keep the result diffable.
13 min
· 14 min
Validate the user's JWT once at API Gateway, pass identity downstream as a header, and close the bypass, spoofing and revocation gaps that design opens.
14 min
· 9 min
How I structure Google Cloud IAM so people get access through groups, workloads get one keyless service account each, and every grant is small and auditable.
9 min
· 11 min
Swap service account keys in GitHub secrets for short-lived OIDC tokens, lock the trust to your own repo, and deploy to Cloud Run with no JSON key.
11 min