CloudConsole

IAM access key audit: old and unused keys, users without MFA, and the root user

A tool in the CloudConsole app for iPhone and Android · read-only · free for one account

Short answer

Long-lived access keys and console passwords without MFA are how AWS accounts get taken over. CloudConsole’s IAM access audit lists active access keys older than 90 days, keys not used for 90 days or never used, console users without an MFA device, and whether the root user has MFA or access keys, with a Deactivate button for keys.

IAM access audit: four findings, root user with MFA and no keys, a 200-day-old key, a never-used key and console users without MFA
IAM access audit
The Tools list: Cost by resource, Waste finder, VPC IP usage, Find an IP, Open by ARN, Schedules, Service quotas and the S3 and IAM audits
Services → Tools

What it checks

Open Services → Tools → IAM access audit. It checks every IAM user in the account and the root user:

  • Root user: whether it has MFA, and whether it has access keys. Nothing should sign requests as root, so root keys are always a finding; the fix is in the console, signed in as root.
  • Old access keys: active keys created more than 90 days ago, with their age (“200 days old”).
  • Unused access keys: active keys not used for 90 days, or never used. A brand-new key isn’t called unused until it has had 90 days, so a key you created this morning doesn’t show up.
  • Console users without MFA: users with a console password and no MFA device, with when the password was last used.

For each key it shows when it was last used and by which service, which is what tells you what will break if you turn it off. The usual sequence for an old key that is still in use: create a second key, move the user or system over, check the old one stops being used, then deactivate it, and delete it later.

Deactivate is the IAM screen’s own action: a Pro change with a typed confirmation, recorded in the activity log, and reversible, because an inactive key can be made active again. The app can’t add an MFA device for another user; each user does that in the AWS console under Security credentials.

90 days is the age most security standards use for rotation, and it is the age AWS Security Hub’s IAM controls check for unused credentials. If your organisation uses IAM Identity Center or roles everywhere, the ideal result is no IAM users with keys at all.

How it works, and what it can read

What it readsIAM actions
Root user MFA and keysiam:GetAccountSummary
Users, console passwords and MFA devicesiam:ListUsers, iam:GetLoginProfile, iam:ListMFADevices
Access keys and their last useiam:ListAccessKeys, iam:GetAccessKeyLastUsed
Deactivate (Pro, a change)iam:UpdateAccessKey

ViewOnlyAccess leaves out iam:GetAccessKeyLastUsed; add it, or the audit can only report key age.

All of these reads are in the AWS managed ReadOnlyAccess policy. ViewOnlyAccess leaves some out; Recommended permissions lists the extras. If one call is denied, the rest of the tool still works and says which permission is missing.

Nothing leaves your phone. The app signs each request with your own credentials, which stay in the iOS Keychain or Android Keystore, and sends it straight to AWS. There is no CloudConcur server in between, so we never see your resources or the results.

Free to look, Pro to fix. Every check only reads, so it works on the free plan (one account) and in the built-in demo. Where the tool offers a fix, it is the app’s usual action: it needs Pro, goes through the confirmation you set for that account and is recorded in the activity log on your phone.

Do it without the app

The IAM credential report has most of this in one CSV, one row per user plus <root_account>, with mfa_active, access_key_1_last_rotated and access_key_1_last_used_date columns. AWS regenerates it at most every 4 hours:

aws iam generate-credential-report
aws iam get-credential-report --query Content --output text | base64 -d > credential-report.csv

Or per user and key:

aws iam get-account-summary --query 'SummaryMap.[AccountMFAEnabled,AccountAccessKeysPresent]'
aws iam list-access-keys --user-name deploy-bot
aws iam get-access-key-last-used --access-key-id AKIAIOSFODNN7EXAMPLE
aws iam list-mfa-devices --user-name alice

To turn a key off without deleting it:

aws iam update-access-key --user-name deploy-bot \
  --access-key-id AKIAIOSFODNN7EXAMPLE --status Inactive

Questions

Does deactivating a key delete it?

No. An inactive key stops working but can be made active again, which makes it the safe first step. Delete it once nothing has complained for a while.

Why isn’t a new, unused key flagged?

A key only counts as unused once it is 90 days old and hasn’t been used in that time, so keys created for a rotation aren’t reported before they’ve had a chance to be used.

Can it check users in other accounts?

Yes, one account at a time: switch account in the app. Each account needs its own read permissions.

Try it on your own account

CloudConsole is on the App Store for iPhone and Google Play for Android. Every tool also works in the built-in demo, if you’d rather look around before connecting an account.

Details: Tools for your AWS account in the help centre.