Cloud IAM Core Concepts and Components
What You'll Learn
You'll understand the five foundational building blocks that make cloud IAM work: identities, principals, resources, actions, and policies.
The Building Blocks of Cloud IAM
Think of cloud IAM as a permission system built from five core components that answer key questions:
Identities
What you are in the cloud system. An identity could be a user account (alice@company.com), a service account (app-backend-prod), or a federated identity from your corporate directory. Identities are the "nouns" in your security statements.
Principals
Who is trying to do something right now. When an identity authenticates and makes a request, it becomes a principal. Think of this as the active, authenticated version of an identity—like showing your ID badge when entering a building.
Resources
The things you want to protect. In cloud environments, these are objects like storage buckets, virtual machines, databases, or API endpoints. Each resource has a unique identifier (ARN, URI, etc.) and can have permissions attached to it.
Actions
The operations that can be performed on resources. Examples include read, write, delete, start, stop, or more specific operations like storage:GetObject or compute:CreateInstance. Actions define the verbs of what's possible.
Policies
The rules that tie everything together. A policy is a document that says "Principal X can perform Action Y on Resource Z under Condition W." Policies are where you express access control decisions in a structured, enforceable format.
How They Work Together
When a principal tries to access a resource, the IAM system evaluates policies to determine: Does this principal have permission to perform this action on this resource? This is the authorization decision at the heart of cloud security.
Key Takeaway: Cloud IAM operates through five core components—identities (who you are), principals (authenticated actors), resources (protected objects), actions (operations), and policies (permission rules)—that work together to enforce access control decisions.