Least privilege for human users in AWS starts with permission sets, not IAM users
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Human users in AWS get permissions through IAM Identity Center permission sets, federated roles or IAM users. AWS's IAM guide, read 16 Nov 2026, recommends temporary credentials, Access Analyzer unused access findings and generated policies. This guide gives the steps, the policies to avoid and what to measure.
Open the calculator ยท All guides
Human users reach AWS through permission sets, federated roles or IAM users
AWS's IAM best practices page defines human identities as the administrators, developers, operators and consumers of your applications, and tells you to require them to use federation with an identity provider and temporary credentials. For central management it recommends AWS IAM Identity Center.
In IAM Identity Center a permission set is a template that holds one or more IAM policies. When you assign a permission set to a user or group, AWS says IAM Identity Center creates a matching IAM role in each target account and attaches the policies to it. Changing the permission set updates those roles.
The other routes are IAM users with console passwords or access keys, and the account root user. AWS lists narrow cases where an IAM user is still needed, such as third-party clients that do not support IAM Identity Center. Where an IAM user or root user exists, AWS says to require multi-factor authentication.
Each route is a place where privilege accumulates. Privilege creep in AWS usually shows up as a permission set that began as AdministratorAccess and was never replaced, or as an IAM user whose keys nobody has used for a year.
AWS provides three tools that compare granted access with used access
IAM Access Analyzer unused access analyzers monitor all IAM roles and users in an organization or account. AWS documents findings for unused roles, unused IAM user access keys and passwords, and unused service-level and action-level permissions within a usage window you set. AWS states that external access findings are free and that unused access findings are charged.
IAM last accessed information reports the services and actions an identity last used. AWS documents a tracking period of at least 400 days for service information, with action tracking that began on different dates by service (Amazon S3 on 12 April 2020, EC2, IAM and Lambda on 7 April 2021, other services on 23 May 2023). Recent activity appears in the console within four hours.
IAM Access Analyzer policy generation reads AWS CloudTrail events for a date range of up to 90 days and produces a policy template that holds the actions and services the user or role used. You review it, add resources and conditions, and attach it in place of the broad policy.
AWS's permission set guidance describes the same sequence: run Access Analyzer against principals that use AWS managed policies, learn what they use, then write or generate a narrower policy. The wider method is in the first 90 days and the least privilege policy template.
Steps to bring human access in an AWS organization to least privilege
- List every route people use: permission sets, federated roles, IAM users, root. Record which accounts each permission set is assigned to.
- Move people from IAM users to IAM Identity Center or another federated route, so credentials are temporary.
- Give each administrator a second, narrower permission set. AWS's own example assigns PowerUserAccess for development work and keeps AdministratorAccess for administration, and users choose the narrower role in the access portal.
- Create an unused access analyzer for the organization and work the findings by oldest unused first.
- For each remaining broad permission set, generate a policy from CloudTrail activity (up to 90 days), edit it, test it in a non-production account, then replace the broad policy.
- Disable or delete IAM user access keys and passwords that the analyzer reports as unused, using access last used data to confirm.
- Set a review date for every permission set and repeat the analyzer review on that date.
Policies and credentials to avoid for human users
| Policy or credential | Documented reason (AWS, read 16 Nov 2026) | Use instead |
|---|---|---|
| AdministratorAccess | AWS describes it as granting all actions for all AWS services on all resources in the account. | A job-function or custom permission set; a separate administrator permission set used only for administration. |
| PowerUserAccess as a permanent default | AWS says it allows all actions for all services except IAM, AWS Organizations and Account Management, so it is a step down from administrator rather than a least-privilege set. | A permission set generated from the user's CloudTrail activity. |
| IAM user access keys for people | AWS says IAM users with access keys are an account security risk and that keys in the shared credentials file are stored in plaintext. | IAM Identity Center sign-in with temporary credentials. |
| Root user access keys | AWS says not to use root credentials to create access keys. | Root only for tasks that require it, with MFA. |
| Unmodified AWS managed policies | AWS says managed policies may not grant least privilege for your use case because they serve all customers. | Customer managed policies scoped to the task. |
Measure granted permissions against used permissions per principal
For each permission set and IAM user, count the services granted and the services last accessed in the tracking window, and record the ratio per principal. Use the unused access analyzer finding count as a second series: unused roles, unused keys and passwords, unused permissions.
Also count principals holding AdministratorAccess and the number of accounts each is assigned to. These counts come from the assignments themselves, so they need no usage data and can be taken today. The Access Debt Calculator on this site turns granted and used counts into a single figure, and the principle of least privilege explains why the unit is the permission rather than the person.
Related guides: Azure human identities and Google Cloud human identities.
Related pages
Sources
- AWS IAM User Guide: Security best practices in IAM, read 16 Nov 2026
- AWS IAM Identity Center User Guide: Permission sets, read 16 Nov 2026
- AWS IAM User Guide: Using IAM Access Analyzer, read 16 Nov 2026
- AWS IAM User Guide: IAM Access Analyzer findings, read 16 Nov 2026
- AWS IAM User Guide: Refine permissions using last accessed information, read 16 Nov 2026
- AWS IAM User Guide: IAM Access Analyzer policy generation, read 16 Nov 2026
- AWS IAM User Guide: AWS managed policies for job functions, read 16 Nov 2026
- AWS IAM User Guide: Manage access keys for IAM users, read 16 Nov 2026
Last reviewed 16 Nov 2026.