Why Assuming roles for temporary access in AWS? - Purpose & Use Cases

The Big Idea

What if you could grant access that disappears automatically when no longer needed?

The Scenario

Imagine you have multiple team members who need access to different parts of your cloud resources. You try to give each person permanent access by creating separate user accounts with fixed permissions.

Later, when someone changes roles or leaves, you have to manually find and remove their access everywhere.

The Problem

This manual approach is slow and risky. You might forget to remove access, leaving security holes open.

Also, managing many permanent accounts with different permissions becomes confusing and error-prone.

The Solution

Assuming roles lets users temporarily get the exact permissions they need, only when they need them.

This means no permanent access is given, reducing risk and making management easier.

Before vs After

✗ Before

Create user with fixed permissions
Manually update permissions when roles change

✓ After

User assumes a role temporarily
Permissions expire automatically after use

What It Enables

It enables secure, flexible access control that adapts instantly to changing needs without permanent permission changes.

Real Life Example

A developer needs access to a database only during a deployment. Instead of permanent access, they assume a role for a short time, then lose access automatically after deployment.

Key Takeaways

Manual permanent access is hard to manage and risky.

Assuming roles provides temporary, precise permissions.

This improves security and simplifies access control.