The request came in at 2:04 a.m.
An S3 bucket, production data, access locked down by policy.
You needed AWS CLI access for five minutes—just enough to fix it, not enough to expose a risk.
That is the promise of AWS CLI Just-In-Time Access Approval: delivering tight, temporary permissions exactly when you need them, without leaving a door open. It’s the opposite of static credentials sitting in a dev’s config file for months. This approach controls blast radius, enforces policy, and keeps your security team sane.
Why Just-In-Time Access Matters
Long-lived IAM keys are a liability. If they leak, they linger. AWS CLI Just-In-Time Access approval solves that by flipping the model: no access until approved, access expires automatically.
This balances agility and compliance. Engineers keep moving. Auditors get a clean trail. Security posture improves in minutes, not months.
How It Works
You request AWS CLI access through an approval workflow. The request could be triggered via a web portal, Slack bot, or CLI wrapper.
A designated approver reviews the context: which IAM role, which duration, what purpose. If approvers agree, credentials are generated on the spot, scoped to exactly what’s needed.
When the timer expires, so does your access. No cleanup scripts. No forgotten keys.