IAM Core Concepts: Identities and Resources
What you'll learn: How IAM connects "who can do something" (identities) with "what they can access" (resources) in cloud environments.
The Core Relationship
Think of IAM like a building's security system. Identities are the people with key cards (users, applications, services), and resources are the rooms, equipment, and data they might need to access (databases, storage, virtual machines, networks).
IAM's job is to answer: "Should this identity be allowed to access that resource?"
Understanding Identities
An identity is anything that can request access to cloud resources:
- Users: Individual people (developers, admins)
- Service accounts: Applications or automated processes
- Groups: Collections of users managed as a unit
- Roles: Temporary identities that can be assumed
Each identity must first authenticate (prove who they are), as we covered in the previous lesson.
Understanding Resources
A resource is any cloud asset that can be accessed or managed:
- Compute instances (VMs, containers)
- Storage buckets and databases
- Networks and load balancers
- Other cloud services and APIs
Resources are the "what" in "what can be accessed."
The Connection
IAM creates policies that define the relationship: which identities can perform which actions on which resources. This is authorization in action.
For example: "User Alice can read data from StorageBucket-A" or "ServiceAccount-B can restart VM-instance-123."
Key Takeaway: IAM manages the fundamental relationship between identities (who) and resources (what), ensuring only authorized access occurs in your cloud environment.