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.