Cloud IAM — Roles, Policies and Service Accounts
How Google Cloud decides who can do what: roles bound to principals on the resource hierarchy, IAM Conditions, deny and principal access boundary policies, service accounts without keys, impersonation, Workload Identity Federation, Privileged Access Manager, and the 403s interviewers ask you to debug.
Sign up free to read the full topic
More Cloud topics
- Bigtable — Wide-Column NoSQL at Scale
- CDK — Cloud Development Kit
- Cloud Build: build configs, triggers, private pools and build identity
- Cloud CDN — caching on the global load balancer, and Media CDN
- Cloud Deploy: delivery pipelines, canary rollouts, verification and rollback
- Cloud DNS — public, private and hybrid zones
- Cloud Interconnect
- Cloud KMS — Keys, Rotation and CMEK
- Cloud Load Balancing — Application and Network Load Balancers
- Cloud Logging: the Log Router, log buckets, sinks and Observability Analytics
- Cloud Monitoring: metrics, alerting policies, uptime checks and SLOs
- Cloud NAT
Start free on Cariara · Coding problems · System design studio