All Tools View Categories About Contact Privacy

AWS Managed Policy Lookup

Search AWS-provided (AWS managed) IAM policies by name — exact ARN and a one-line description of what each grants.

Curated selection of ~25 of AWS's 1,000+ managed policies — verify current permissions in the IAM console before relying on them. Runs entirely in your browser.
Policy nameARNWhat it grants

About AWS Managed Policy Lookup

Attaching the right AWS managed policy means first knowing it exists and remembering its exact name and ARN — AWS ships over 1,000 of these ready-made, AWS-maintained policies, and typing one wrong (or confusing AmazonS3ReadOnlyAccess with AmazonS3FullAccess) is an easy mistake. AWS Managed Policy Lookup is a searchable table of commonly used AWS managed policies with their exact ARN and a one-line description of what each grants, so you can find and copy the right one quickly.

Every AWS managed policy's ARN follows the pattern arn:aws:iam::aws:policy/PolicyName, using the literal account id aws instead of your own 12-digit account id — the giveaway that a policy is AWS-managed rather than something your own account created. A handful of policies meant for service roles, like AWSLambdaBasicExecutionRole, live under an extra service-role/ path segment, which is easy to miss if you're typing the ARN from memory.

This is a curated subset of roughly 25 of the most frequently referenced managed policies, spanning broad-access policies (AdministratorAccess, PowerUserAccess, ReadOnlyAccess), per-service read-only/full-access pairs (S3, EC2, DynamoDB, SNS, SQS, CloudWatch, RDS, VPC), and a few specialized ones (SecurityAudit, AWSSupportAccess, the Lambda execution role, the EKS cluster policy) — not AWS's complete catalog. Policy contents can also change over time as AWS extends them, so treat the description shown here as a helpful summary and verify the current permissions in the IAM console or AWS CLI before relying on it for an access decision.

Features

  • ~25 curated AWS managed policies spanning broad-access, per-service, and specialized policies.
  • Exact ARN for every policy, including the service-role/ path segment where it applies.
  • One-line description of what each policy grants.
  • Live search across policy name, ARN, and description.
  • One-click copy of any policy's ARN.
  • 100% client-side — a static reference table, nothing sent anywhere.

How to Use

  1. Type a keyword into the search box (e.g. "s3", "read only", "lambda").
  2. Scan the matching rows for the policy name and description.
  3. Click the copy icon to copy that policy's exact ARN.
  4. Verify current permissions in the IAM console before attaching, especially for anything security-sensitive.

Examples

Example 1 — granting a new engineer read access. Search "read only" to compare ReadOnlyAccess (all services) against ViewOnlyAccess (metadata only, no resource content) and pick the narrower one that fits.

Example 2 — a Lambda execution role. Search "lambda" to find AWSLambdaBasicExecutionRole and its service-role/-prefixed ARN for CloudWatch Logs permissions.

Example 3 — an auditor role. Search "audit" to find SecurityAudit, which reads security configuration across services without granting write access to anything.

Benefits

  • Saves time versus hunting through the IAM console for an exact policy name and ARN.
  • Reduces ARN typos — copy the exact string instead of retyping it.
  • Flags the service-role/ path quirk that's easy to miss on policies like AWSLambdaBasicExecutionRole.
  • Honest about its limits — a curated subset with an explicit prompt to verify current permissions before relying on them.

Frequently Asked Questions

Is this every AWS managed policy?
No. AWS provides over 1,000 AWS managed policies across all of its services, and this page covers a curated selection of roughly 25 of the most commonly used ones — not a complete catalog. For the full, authoritative, up-to-date list, browse Policies in the IAM console (filtered to "AWS managed") or run <code>aws iam list-policies --scope AWS</code>.
Can I trust the description shown here to be exactly what the policy currently grants?
Treat it as a helpful summary, not a substitute for checking the real thing. AWS managed policies are versioned and their contents can change over time as AWS adds permissions for new features. Before relying on a policy for an access decision, view its current JSON in the IAM console or with <code>aws iam get-policy-version</code> to see exactly what it grants today.
What is the difference between an AWS managed policy and a customer managed policy?
An AWS managed policy is created and maintained by AWS itself, lives under the special account id "aws" in its ARN (e.g. <code>arn:aws:iam::aws:policy/ReadOnlyAccess</code>), and cannot be edited — only attached or detached. A customer managed policy is one you create and maintain in your own account, with your own 12-digit account id in its ARN, and full edit control.
Why does AWSLambdaBasicExecutionRole have "service-role/" in its ARN but the others don't?
A small number of AWS managed policies — mostly ones meant to be attached to a service-linked or service role rather than a human identity — are namespaced under a <code>service-role/</code> path segment in their ARN. AWSLambdaBasicExecutionRole is the most common example: its full ARN is <code>arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole</code>, not the bare <code>arn:aws:iam::aws:policy/AWSLambdaBasicExecutionRole</code> you might expect by analogy with the others.
What is the difference between PowerUserAccess and AdministratorAccess?
AdministratorAccess grants unrestricted access to every AWS service and resource, including full IAM control. PowerUserAccess grants the same broad access to build and run workloads but explicitly excludes the ability to manage IAM users, groups, roles, and policies (and AWS Organizations) — so a PowerUserAccess principal cannot grant itself or anyone else additional permissions.
Does this tool call AWS or verify anything against a live account?
No. It is a static, curated reference table with a client-side search box — nothing is looked up from or sent to AWS.