AWS IAM actions are named service:ActionName, and AWS lists 22,556 of them across 457 services
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
An AWS IAM action is a service prefix and an action name, such as s3:GetObject. AWS's service reference, fetched 16 Nov 2026, lists 22,556 actions in 457 services, led by ec2 with 834. Each action has an access level, resource types and condition keys in the Service Authorization Reference.
Open the workbench ยท All guides
An action is a prefix, a colon and a name
AWS says you specify an action with a service namespace as the prefix, such as iam, ec2, sqs, sns or s3, followed by the name of the action to allow or deny. The name must match an action the service supports. The prefix and the name are case insensitive, so iam:ListAccessKeys equals IAM:listaccesskeys.
The prefix is not always the product name you know. AWS IAM Identity Center actions use sso, CloudWatch Logs uses logs and Access Analyzer uses access-analyzer. The workbench takes the prefix from AWS's reference and reports any action in a policy that matches nothing in it, with a medium-severity finding, because a mistyped action name in an Allow statement grants nothing and in a Deny statement denies nothing.
Four services hold just over nine percent of all actions
The service reference of 16 Nov 2026 lists 457 services and 22,556 actions. ec2 has 834 actions, sagemaker 460, connect 388 and quicksight 359; chime has 316, glue 306, iot 293 and datazone 278. Nineteen services list exactly one action.
| Service prefix | Actions | Share of 22,556 |
|---|---|---|
| ec2 | 834 | 3.7 percent |
| sagemaker | 460 | 2.0 percent |
| bedrock | 269 | 1.2 percent |
| iam | 190 | 0.8 percent |
| s3 | 180 | 0.8 percent |
| lambda | 135 | 0.6 percent |
| sso | 126 | 0.6 percent |
| organizations | 63 | 0.3 percent |
| kms | 58 | 0.3 percent |
| sts | 16 | 0.1 percent |
The reference has three parts for each action
For each service, the Service Authorization Reference lists actions, the resource types an action can be scoped to, and the condition keys that apply. The workbench reads the same three for each action from the machine-readable reference, together with the access level. AWS adds a machine-readable form: service reference information in JSON, which includes actions, resources and condition keys, available from servicereference.us-east-1.amazonaws.com. AWS says changes to the service reference can take up to 24 hours to appear.
On 21 Oct 2026 AWS expanded the machine-readable reference with every aws: global condition key in one file, a ServiceName field that maps service identifiers to human-readable names, and an IsDataPlane property that marks which actions are data plane operations. The workbench's snapshot of 16 Nov 2026 records actions, access levels, resources and condition keys; it does not use the data plane property.
Counts change, so every count carries a date
The Policy Generator that AWS publishes lists 22,674 action entries in its own configuration, 118 more than the service reference, on the same day. A list of actions without a date cannot be compared with another list. The workbench stores the date of its reference snapshot with the data and prints it with the counts it shows.
To use the list, begin with the service you need. Then read the resource types for the actions you plan to allow, and use them in the Resource element instead of "*". The pages on wildcards and access levels cover what the patterns match and how each action is classified.
Related pages
Sources
- AWS service reference information, read 16 Nov 2026
- Simplified AWS service information for programmatic access, read 16 Nov 2026
- Actions, resources and condition keys for AWS services, read 16 Nov 2026
- IAM JSON policy elements: Action, read 16 Nov 2026
- AWS Service Reference Information update, read 16 Nov 2026
- AWS Policy Generator configuration (policies.js), read 16 Nov 2026
Last reviewed 16 Nov 2026.