Library · concept
Identity and access management
Decide who can do what to which resource: least-privilege policies, roles with temporary credentials, explicit denies, and identities for machines as well as people.
Identity and access management appeared in 22% of the DevOps job descriptions we read, and it is central to cloud and security roles. Most cloud breaches involve credentials or permissions that were broader than they needed to be.
The examples use AWS IAM policy syntax. They run locally against moto, a library that emulates AWS and, in the mode used here, enforces IAM policies, so every "allowed" and "denied" below was produced by evaluating the policy. The concepts map directly to Azure role assignments and Google Cloud IAM.
Beginner lessons for Identity and access management are being written.
Advanced lessons for Identity and access management are being written.
- 1BeginnerHost a static site with a CDN, TLS and your own domain
- 2IntermediateA cloud network and service in Terraform, reviewed like code
- 3IntermediateAudit and tighten cloud permissions
- 4IntermediateGuardrails that make insecure cloud setups impossible
- 5AdvancedA cloud security posture review with fixes as code
- 6AdvancedA field-encryption and secrets service done right
- 7AdvancedA secure software delivery pipeline
- 8AdvancedA secure software supply chain with policy as code