What You'll Learn
You'll discover how permission boundaries act as safety nets that cap the maximum permissions any identity can have, preventing accidental or malicious privilege escalation.
What Are Policy Boundaries?
A permission boundary is a special type of IAM policy that defines the maximum permissions an identity (user or role) can ever have—even if other policies grant broader access. Think of it as a fence around a playground: no matter how fast you run or how high you jump, you can't leave the enclosed area.
Permission boundaries don't grant permissions; they limit them. An identity needs both a permission boundary to allow something and a regular policy to grant it. If either says "no," the action is blocked.
Why Use Permission Boundaries?
Imagine you delegate user creation to a team lead. Without boundaries, they could create users with full admin access—potentially even exceeding their own permissions. A permission boundary prevents this by ensuring any user they create cannot exceed a predefined capability ceiling.
Real-World Analogy
You're managing a company credit card program. Each department head can issue cards to their team, but you set a 10,000 expense, the boundary blocks it. The cardholder still needs approval for individual purchases (regular policies), but the ceiling is absolute.
Guardrails in Action
Common guardrail scenarios:
- Developer sandboxes: Developers can create resources but never modify IAM or billing settings
- Delegated administration: Managers can create users, but those users cannot touch security or compliance controls
- Third-party integrations: External services get limited scope boundaries regardless of assigned roles
Key Takeaway: Permission boundaries set maximum permission limits that cannot be exceeded, preventing privilege escalation even when permissions are delegated or inherited.