Not all IAM users have MFA
Without MFA, a leaked password equals account takeover. Force it via policy.
support/cloud-platforms/iam-mfa-enforcementsteps: 4
Try this first
- Write a policy denying everything until MFA is active, except self-service MFA setup
- Attach to a group and put all users in it
- Announce 1 week ahead with authenticator-app instructions
- Verify via IAM credential report that everyone has MFA
When to bring us in
SMS MFA is weak. Use TOTP or preferably a security key.
See also
- Everyone logs in with the AWS root accountRoot is for emergencies and billing. Day-to-day work belongs in IAM users or SSO.
- Every developer has AdministratorAccessAdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.