# The AWS Policy Generator builds five policy types, and this workbench reads and checks them

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

AWS's own Policy Generator builds IAM, S3 bucket, SNS topic, SQS queue and VPC endpoint policies from a form. Its published configuration, read on 16 Nov 2026, lists 477 services and 55 condition operators. This workbench builds five different types, labels access levels, expands wildcards and runs six checks, all in the browser.

## AWS's generator is a form that writes a policy document

The AWS Policy Generator is a web application at awspolicygen.s3.amazonaws.com. A plain page fetch on 16 Nov 2026 returned only the title, because the form is drawn by scripts, so this page describes the tool from the configuration file that the page loads, policies.js, which this site also fetched that day.

The configuration lists five policy types: an IAM policy, an S3 bucket policy, an SNS topic policy, an SQS queue policy and a VPC endpoint policy. It lists 477 services with 22,674 action entries in total, and 55 condition operators, among them the IfExists forms and the Null operator. For each service it records a string prefix, a list of actions and a flag named HasResource. No access level field is present in the configuration (none found on 16 Nov 2026).

## AWS offers other ways to write a policy as well

The IAM console creates customer managed policies three ways, according to AWS: the JSON editor, where you paste and customize an example; the visual editor, which does not need JSON knowledge; and import, where you copy an existing AWS managed or customer managed policy and change it. When you create or edit a JSON policy, IAM reports syntax errors and Access Analyzer adds policy checks with recommendations.

A second route is generation from activity: Access Analyzer reads CloudTrail events from up to 90 days and produces a policy that covers what the entity used. A third is IAM Policy Autopilot, an open source tool that AWS describes as analyzing your code to create scoped-down policies. On 18 Aug 2026 AWS announced that it also accepts a Terraform plan file and names resource ARNs instead of wildcards where possible.

## This workbench differs in what it builds and what it shows

The workbench builds identity policies, service control policies, resource control policies, permissions boundaries and role trust policies. AWS's generator builds the five types above, which include three resource policies (S3, SNS and SQS), and the workbench does not build those. The overlap is the identity policy.

Beyond the type list, the differences are in what the workbench adds to the form. It expands each wildcard against AWS's service authorization reference, 457 services and 22,556 actions fetched on 16 Nov 2026, and prints the count. It labels every action with one of the five access levels. It reads a pasted policy as well as building one. It runs six checks and links each finding to the AWS page that explains it. It runs in your browser and uploads nothing.

| Feature | AWS Policy Generator (per its configuration) | This workbench |
| --- | --- | --- |
| Policy types | IAM, S3 bucket, SNS topic, SQS queue, VPC endpoint | Identity, SCP, RCP, permissions boundary, role trust |
| Services and actions | 477 services, 22,674 action entries | 457 services, 22,556 actions |
| Access levels | None found in the configuration | List, Read, Write, Permissions management, Tagging |
| Wildcard expansion | None found in the configuration | Count and levels for each wildcard |
| Reads an existing policy | None found in the configuration | Yes, and explains it in plain sentences |
| Condition operators | 55 | Set from the same AWS operator list |

## The two reference sets differ by 118 actions because of when and how they were read

The generator's action total, 22,674, and the workbench's, 22,556, differ by 118. Both came from AWS sources on 16 Nov 2026, but they are different files: the generator reads its own configuration, and the workbench reads the service reference AWS publishes for automation. AWS says changes to the service reference can take up to 24 hours to appear. The gap shows why a list of actions should carry the date it was read, which every count on this site does.

## A generated policy still needs reading

A form can only offer the actions it knows. It cannot tell you whether an allowed set of write actions on every resource is intended. After building a policy with either tool, paste it into the workbench to see the number of actions and the findings. The page on [AWS IAM actions](/aws-iam-actions/) explains how actions are named, and [the wildcards page](/iam-wildcards/) explains what a star covers.

## Related pages

- [AWS Managed Policies and Why Broad Ones Are Risky](/aws-managed-policies/)
- [AWS Trust Policy: Principals and Conditions](/aws-trust-policy/)
- [IAM Condition Keys, Operators and IfExists](/condition-keys/)
- [All of them](/guides/)

## Sources

- AWS Policy Generator: https://awspolicygen.s3.amazonaws.com/policygen.html (read 16 Nov 2026)
- AWS Policy Generator configuration (policies.js): https://awspolicygen.s3.amazonaws.com/js/policies.js (read 16 Nov 2026)
- Create IAM policies (console): https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html (read 16 Nov 2026)
- IAM Access Analyzer policy generation: https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-generation.html (read 16 Nov 2026)
- IAM Policy Autopilot now supports Terraform plan files: https://aws.amazon.com/about-aws/whats-new/2026/08/iam-policy-autopilot-now-supports-terraform-plan-files (read 16 Nov 2026)
- AWS service reference information: https://servicereference.us-east-1.amazonaws.com/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/aws-policy-generator/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
