IAM User Access Key Older Than 90 Days
A long-lived key that has never been rotated stays valid wherever it has leaked to, a repository, a log, an old laptop.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Rotate IAM user access key.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- IAM Users on AWS
- The fix, by hand
- Go to IAM Console → Users → select the user → Security credentials.
- Create a new access key.
- Update all applications, scripts, and CI/CD pipelines with the new key.
- Verify the new key is working correctly.
- Deactivate the old key and monitor for errors.
- Delete the old key after confirming no breakage.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-082- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.