IAM access levels sort 22,556 actions into five groups, and Write is more than half
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
AWS classifies every IAM action as List, Read, Write, Permissions management or Tagging. In the service reference fetched 16 Nov 2026, 11,606 of 22,556 actions are Write, 6,005 Read, 3,790 List, 721 Tagging and 434 Permissions management. The classification differs from the action name in some cases.
Open the workbench ยท All guides
AWS defines five access levels
AWS defines the levels in its documentation on policy summaries. List is permission to list resources to determine whether an object exists, without seeing contents. Read is permission to read, but not edit, the contents and attributes of resources. Write is permission to create, delete or modify resources. Tagging is permission to perform actions that only change resource tags. Permissions management refers to actions that control access within AWS services, including IAM and non-IAM identity permissions, but excludes network-level controls such as security groups.
AWS gives examples. S3 ListBucket is List. S3 GetObject is Read. S3 CreateBucket, DeleteBucket and PutObject are Write. IAM TagRole and UntagRole are Tagging, while CreateRole is Write because it does more than add a tag. S3 PutBucketPolicy and DeleteBucketPolicy are Permissions management. AWS adds a tip: restrict or regularly monitor policies that include the Permissions management level.
Write dominates, and Permissions management is the smallest group
The figures below count every action in AWS's service reference of 16 Nov 2026. Shares are of the 22,556 total.
| Access level | Actions | Share |
|---|---|---|
| Write | 11,606 | 51.5 percent |
| Read | 6,005 | 26.6 percent |
| List | 3,790 | 16.8 percent |
| Tagging | 721 | 3.2 percent |
| Permissions management | 434 | 1.9 percent |
Permissions management is concentrated in a few services
The 434 Permissions management actions spread over 101 services. glue has 36, s3 27, ec2 23, iam 23, quicksight 19 and redshift 13. AWS's page says most IAM and AWS Organizations actions have this level. In the 16 Nov 2026 reference, 23 of the 190 IAM actions and 5 of the 63 Organizations actions carry it, so the sentence in the documentation and the data in the reference differ. The workbench follows the reference, since each action is individually classified there.
Among the IAM actions, iam:AttachRolePolicy is classified as Permissions management and iam:CreateRole as Write. Within the s3:Put* group, twelve of 40 actions are Permissions management, among them s3:PutBucketPolicy and s3:PutObjectAcl.
Verbs and levels disagree in places
Names are a poor guide. Across all services, 31 actions whose names start with Get are classified Write, for example cognito-idp:GetTokensFromRefreshToken. AWS classifies kms:Decrypt as Write, and iam:PassRole as Write. ReadOnlyAccess, an AWS managed policy, expands to 7,202 actions, eight of them Write and three Permissions management. A reviewer who reads only verbs would call those reads.
The workbench labels each action with its level, then counts Write and Permissions management actions on Resource "" for its wildcard finding. A statement with Resource "" and only List and Read actions is not reported as that finding; one that adds a Write action is.
Policy summaries in the console use the same levels
In the IAM console, policy summaries show an access level summary for each service in a policy. The summary says Full when the policy allows all the actions within a level and Limited when it allows some but not all. AWS adds that a service the summary does not recognize shows an empty entry, which can mean a typo in the service name, a service without summary support or a service in preview. The summary is a quick way to see the shape of a policy; the workbench adds the counts. See the managed policies page for counts of large AWS policies by level.
Related pages
Sources
- Access levels in policy summaries, read 16 Nov 2026
- AWS service reference information, read 16 Nov 2026
- Actions, resources and condition keys for AWS services, read 16 Nov 2026
- ReadOnlyAccess, AWS managed policy reference, read 16 Nov 2026
Last reviewed 16 Nov 2026.