AWS Builder Center

The AWS Security Feature Almost Nobody Talks About (But Should)

IAM Access Analyzer has a feature most people never open: Unused Access findings. It quietly identifies forgotten permissions, dormant roles, and unused access keys before an attacker finds them first. Here's why it might be the highest-impact, lowest-effort security fix you're not using.

Sandip Ghorai | Cloud & AI Developer

The Feature Nobody Talks About

Ask most AWS users about IAM security tools and they'll mention Access Analyzer's ability to find public or cross-account resources. Almost nobody mentions its other capability: Unused Access findings, a feature that quietly identifies permissions your users and roles have but never actually use. It's been available for a while, and it's one of the highest-impact, lowest-effort security wins in AWS, yet it barely gets discussed.

Why This Matters More Than People Realize

Over-permissioning is one of the most common root causes behind real breaches. It's rarely a single obviously dangerous permission that causes damage — it's the accumulation of unused access nobody remembers granting: a role that once needed S3 full access for a migration two years ago, a user with EC2 permissions from a project that ended, an old service account nobody has touched since a departed engineer set it up.
Every one of these is a door left unlocked. An attacker who compromises even a low-privilege credential can often move laterally simply because permissions were never cleaned up, not because they were deliberately over-granted.

What Unused Access Findings Actually Does

IAM Access Analyzer continuously observes how permissions are actually used, then flags:
  • Unused IAM roles that haven't been active in a set period
  • Unused IAM user access keys
  • Unused permissions within a policy — actions granted but never called
  • Unused password and access key combinations
This isn't a guess based on best practices — it's based on real CloudTrail activity, so the findings reflect what's actually happening in your account, not a generic checklist.

Why It's Underused

Most teams treat IAM as something you configure once and revisit only when something breaks. Cleaning up permissions feels like a low-priority chore compared to shipping features, and without a tool actively surfacing what's unused, nobody goes looking for it. Access Analyzer changes that by pushing the information to you instead of requiring you to hunt for it.

How to Actually Use It

  1. Enable IAM Access Analyzer if you haven't already — it's free to turn on.
  1. Navigate to the Unused Access tab and review the findings — they're organized by role and user, not buried in raw logs.
  1. Start with the highest-risk findings first: unused access keys and unused administrative permissions, before working through smaller unused actions.
  1. Set a recurring calendar reminder to review this monthly. Permissions creep back in constantly as teams change, and this only stays valuable if you actually look at it.

The Real Impact

This feature won't stop a zero-day exploit or a sophisticated nation-state attack. What it does is quietly shrink your attack surface every single month, removing the exact kind of forgotten access that turns a minor compromise into a major breach. In security, the boring, unglamorous work of cleaning up what you already have often prevents more damage than any flashy new detection tool ever will.
If you're only going to check one underused AWS security feature this month, make it this one.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article