Every developer has AdministratorAccess
AdministratorAccess everywhere is convenient now, painful later. Start with role-based policies.
support/cloud-platforms/iam-policy-least-privilegesteps: 4
Try this first
- Inventory who truly needs admin, usually just 1 or 2 people
- Give developers PowerUserAccess or a custom policy without IAM rights
- Enable IAM Access Analyzer to spot unused permissions
- Review each quarter and trim rights nobody uses
When to bring us in
For compliance (ISO, SOC2), least-privilege is baseline. Allocate time.
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.
- Everyone has individual IAM users with their own passwordIdentity Center (formerly AWS SSO) links to your IdP and issues temporary credentials per session.
- Not all IAM users have MFAWithout MFA, a leaked password equals account takeover. Force it via policy.
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.