Skip to content
IAM Policy Generator

AWS managed policies are written by AWS, and the broad ones grant thousands of actions

An AWS managed policy is a standalone policy that AWS creates and maintains, and it cannot be edited. By the workbench's count on 16 Nov 2026, AdministratorAccess grants 22,556 actions, PowerUserAccess 22,292 and ReadOnlyAccess 7,202. AWS says managed policies do not grant least privilege and should be narrowed.

Open the workbench ยท All guides

AWS maintains these policies and changes them without asking

AWS defines an AWS managed policy as a standalone policy that AWS creates and administers, with its own ARN, for example arn:aws:iam::aws:policy/IAMReadOnlyAccess. You cannot change the permissions in it. AWS occasionally updates them, usually when a new service launches or new API calls appear, and the update affects every user, group and role the policy is attached to.

ReadOnlyAccess shows the effect. The policy page read on 16 Nov 2026 shows version v192, edited 13 Nov 2026, three days earlier. AdministratorAccess shows version v1, unchanged since 6 Feb 2015, because its Action "*" already covers any new service.

AWS groups its managed policies into four kinds

  • Full access policies give service administrators full access to one service, for example AmazonDynamoDBFullAccess and IAMFullAccess.
  • Power-user policies give full access to services and resources but do not allow managing users and groups, for example AWSKeyManagementServicePowerUser.
  • Partial-access policies give specific levels of access to a service without permissions management, for example AmazonEC2ReadOnlyAccess.
  • Job function policies align with common IT jobs and are maintained as new services appear. AWS lists Administrator, Billing, Database administrator, Data scientist, Developer power user, Network administrator, Security auditor, Support user, System administrator and View-only user, among others.

Counted against the AWS action reference, broad policies are large

The workbench expanded the JSON of each policy below against AWS's service authorization reference, fetched on 16 Nov 2026 (22,556 actions). Counts are of distinct actions after expanding wildcards and removing any denied actions. The policy documents were read from the AWS managed policy reference the same day.

PolicyActions grantedOf which WriteOf which Permissions management
AdministratorAccess22,55611,606434
PowerUserAccess22,29211,495406
ReadOnlyAccess7,20283
SecurityAudit3,38023
ViewOnlyAccess (job function)2,27920
AmazonEC2FullAccess1,14569632
AmazonS3FullAccess2066529
IAMFullAccess2007423
AmazonSQSFullAccess2083

Read-only is not always read-only, and power user is not small

PowerUserAccess is built from a NotAction statement that excludes iam:, organizations: and account:*, and a second statement that adds back selected actions. That leaves 22,292 actions, 264 fewer than AdministratorAccess. The name suggests a small step down, and the count shows a step of about 1.2 percent.

ReadOnlyAccess carries eight actions the AWS reference classifies as Write and three it classifies as Permissions management, among them s3express:CreateSession, cognito-idp:GetTokensFromRefreshToken and billing:GetResourcePolicy. They are named like reads and classified differently by AWS. This is one reason to read the access level of each action instead of its name; the access levels page covers the five levels.

AWS tells readers to narrow its managed policies

AWS says AWS managed policies do not grant least-privilege permissions, because they serve all customers, and recommends defining customer managed policies specific to your use cases. It suggests copying an AWS managed policy as the start of a customer managed policy, running Access Analyzer to watch what principals use, and then generating a policy from the activity. For job function policies that pass roles to services, AWS says the policies include filters that limit the names of roles that can be passed. The PassRole page explains why.

A list of AWS managed policy pages follows this text, each with its action count on the fetch date.

Sources

  1. Managed policies and inline policies, read 16 Nov 2026
  2. AWS managed policies for job functions, read 16 Nov 2026
  3. AdministratorAccess, AWS managed policy reference, read 16 Nov 2026
  4. PowerUserAccess, AWS managed policy reference, read 16 Nov 2026
  5. ReadOnlyAccess, AWS managed policy reference, read 16 Nov 2026
  6. SecurityAudit, AWS managed policy reference, read 16 Nov 2026
  7. ViewOnlyAccess, AWS managed policy reference, read 16 Nov 2026
  8. AmazonEC2FullAccess, AWS managed policy reference, read 16 Nov 2026
  9. AmazonS3FullAccess, AWS managed policy reference, read 16 Nov 2026
  10. IAMFullAccess, AWS managed policy reference, read 16 Nov 2026
  11. AmazonSQSFullAccess, AWS managed policy reference, read 16 Nov 2026
  12. AWS service reference information, read 16 Nov 2026

Last reviewed 16 Nov 2026.