- likes
- 32
- comments
- 1
Post
A nightly cleanup job doesn't need full admin access. In Lambda Cloud IAM, give it a service identity with InstanceReader and InstanceTerminate scoped to one workspace. Rotate its API key while the job keeps running. Workspaces hold resources. IAM controls what identities can do with them. The demo covers scoping permissions per workspace, giving automated jobs their own service identities and API keys, and managing shared permissions through groups. API key rotation keeps two keys active at once. Verify the replacement before retiring the old one. The job keeps running without a blanket admin role. View Effective Access brings together direct and group-inherited roles across workspaces, so you can audit what an identity can actually do before it runs. Watch the demo and see it all yourself: