IAM access keys older than 90 days
IAM access keys are long-lived credentials. The longer a key lives, the more places it has been copied — and the longer a leaked one stays valid.
Why it matters
Access keys leak into code, CI config, laptops and screenshots; a key that's years old has had years to end up somewhere it shouldn't.
Unused keys are pure risk with no benefit — they're a credential waiting to be found.
How to check for it
- Download the IAM credential report and look at access_key_1_last_rotated / _2 for keys older than 90 days.
- aws iam list-access-keys per user, then aws iam get-access-key-last-used to spot unused keys.
How to fix it
- Rotate: create a new key, update the consumer, disable the old key, verify, then delete it.
- Where possible remove keys entirely — use IAM roles (EC2/ECS/Lambda) or IAM Identity Center for humans.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Why replace keys with roles?
- Roles hand out short-lived, auto-rotating credentials, so there's no long-lived secret to leak or rotate in the first place.