Skip to content
IAM Policy Generator

IAM wildcards in Action cover from 1 to 22,556 actions, and counts show what a star hides

A wildcard in an IAM Action matches many actions, for example s3:* matches 180 and iam:* matches 190 in AWS's service reference fetched 16 Nov 2026, while a bare * matches all 22,556. This page counts what common wildcards expand to, explains NotAction and shows how stars behave in Resource ARNs.

Open the workbench ยท All guides

A star in an action can cover one action or all of them

AWS says you can use multi-character match wildcards () and single-character match wildcards (?) in an Action value to give access to all the actions a product offers, and also as part of an action name. s3: applies to all S3 actions, and iam:AccessKey applies to all IAM actions containing the string AccessKey: CreateAccessKey, DeleteAccessKey, ListAccessKeys and UpdateAccessKey, according to AWS. In the 16 Nov 2026 reference the same pattern matches five actions, because GetAccessKeyLastUsed also contains the string.

AWS also notes that some services let you limit the actions that are available, for example Amazon SQS, where the star then allows only the subset you have shared.

The counts below come from AWS's service reference of 16 Nov 2026

The workbench expands each pattern against the service authorization reference: 457 services and 22,556 actions, fetched 16 Nov 2026. Levels follow AWS's classification. Counts change when AWS adds actions, so each one carries the fetch date.

Action patternActions matchedAccess levels of those actions
*22,556Write 11,606; Read 6,005; List 3,790; Tagging 721; Permissions management 434
ec2:*834Write 521; List 225; Read 63; Permissions management 23; Tagging 2
iam:*190Write 74; List 40; Read 37; Permissions management 23; Tagging 16
s3:*180Read 66; Write 57; List 18; Permissions management 27; Tagging 12
lambda:*135Write 68; Read 32; List 25; Permissions management 8; Tagging 2
kms:*58Write 38; Read 7; List 7; Permissions management 4; Tagging 2
s3:Get*63Read 63
s3:Put*40Write 23; Permissions management 12; Tagging 5
iam:Put*6Permissions management 5; Write 1
ec2:Describe*195List 195

A name prefix does not guarantee an access level

Prefix wildcards such as Get* and List* read as safe. Counted across all 457 services, every action whose name begins with Get is 3,407 actions, of which 3,229 are Read and 124 are List, but 31 are Write and 23 are Permissions management. Names that begin with Put are 607 actions, and 89 of them are Permissions management. The wildcard s3:Put* includes 12 Permissions management actions, among them s3:PutBucketPolicy, s3:PutBucketAcl and s3:PutObjectAcl.

The workbench counts these by level instead of trusting the verb, which is why its findings call out Write and Permissions management actions on Resource "*". The access levels page explains the five levels.

NotAction reverses a statement and grows with every new service

AWS describes NotAction as an advanced element that matches everything except the actions you list, and says actions in NotAction are not affected by the Allow or Deny effect. With Allow, all actions not listed are allowed. With Deny, all not listed are denied, and you must still allow what you want to allow. AWS warns that NotAction with Allow matches all services and actions not explicitly listed and could grant more permissions than intended.

AWS's own example allows every action in every service except IAM, with NotAction "iam:" and Resource "". In the reference of 16 Nov 2026 that is 22,366 actions, which is 22,556 minus the 190 in IAM. The count rises whenever a service launches, with no change to the policy. The workbench flags an Allow statement with NotAction as a high-severity finding for that reason.

Stars in Resource ARNs work within segments

In a Resource ARN you can use * and ? inside the segments separated by colons. AWS says you can't use a wildcard in the service segment, and recommends using wildcards within the segments. When * is the last character of a segment, it can match beyond the colon boundaries. AWS also says a star can replace everything within a segment, including a forward slash that might look like a delimiter, so "arn:aws:s3:::amzn-s3-demo-bucket//test/" matches objects at any depth, such as amzn-s3-demo-bucket/1/2/3/test/4/object.jpg.

The lone Resource "*" is different in kind. AWS's password example uses it safely because ChangePassword affects only the caller's own password. The same star on iam:PassRole is a finding in the workbench, and the PassRole page says why.

Sources

  1. IAM JSON policy elements: Action, read 16 Nov 2026
  2. IAM JSON policy elements: NotAction, read 16 Nov 2026
  3. IAM JSON policy elements: Resource, read 16 Nov 2026
  4. Actions, resources and condition keys for AWS services, read 16 Nov 2026
  5. AWS service reference information, read 16 Nov 2026

Last reviewed 16 Nov 2026.