π Generating and Reading a Credentials Report
Let's generate the report and see what it actually tells us.
Step 1: Generate It

IAM dashboard β Credential report β Download credential report
This produces a CSV.
Step 2: Read the CSV

Open it up. In this training account, there are two entries: the root account and an IAM user (codeveda).
What's in the report:
π When the account was created
π Whether a password is enabled
π Last password use
π Last password change
π Password rotation status
π Whether MFA is on
ποΈ Access key details β creation, rotation, last use
What it shows here:
Root has MFA on β β the IAM user doesn't β
The IAM user has access keys; root doesn't
Why this matters: one report, and you can spot dormant accounts, missing MFA, and stale credentials at a glance.
Step 3: Access Advisor

The second tool. IAM β Users β select codeveda β Access Advisor (or "Last Accessed").

This shows every AWS service the user can access, alongside when each was last actually used.
The insight it surfaces: a user might have access to a dozen services but only touch two or three of them. That gap is exactly what to trim β if someone only uses EC2, there's no reason they still have standing access to everything else.