Skip to main content
IAM Policy Map

AmazonSQSReadOnlyAccess

ReaderAWS managedActiveReviewedShow on mapCompare

Summary

Provides read only access to Amazon SQS via the AWS Management Console. The Amazon SQS Developer Guide says it grants permissions that allow read-only access to Amazon SQS.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess
Default version
v4
Created
Last edited
Services
sqs

Control-plane actions (6)

By access level: 6 Read.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
SQS6 of 206 Read; 0 restricted, 0 conditionalsqs:GetQueueAttributes, sqs:GetQueueUrl, sqs:ListDeadLetterSourceQueues, sqs:ListMessageMoveTasks, sqs:ListQueueTags, sqs:ListQueues
SQS: 6 actions
  • sqs:GetQueueAttributes (Read)
  • sqs:GetQueueUrl (Read)
  • sqs:ListDeadLetterSourceQueues (Read)
  • sqs:ListMessageMoveTasks (Read)
  • sqs:ListQueueTags (Read)
  • sqs:ListQueues (Read)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: all-resources.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants only List and Read actions.

Guidance

Practical scope

The policy is a single statement (AmazonSQSReadOnlyAccess) on Resource "*" with six actions: sqs:GetQueueAttributes, sqs:GetQueueUrl, sqs:ListDeadLetterSourceQueues, sqs:ListQueues, sqs:ListMessageMoveTasks and sqs:ListQueueTags. It contains no sqs:ReceiveMessage action and no send, delete or purge action.

Use cases

  • Give users, groups or roles read-only access to Amazon SQS.

Best practices

  • AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.

Security considerations

  • It applies to all queues and lists them and their attributes, dead-letter source queues, message move tasks and tags.
  • Amazon SQS added sqs:ListQueueTags and sqs:ListMessageMoveTasks to this policy after it was first published, and updates to an AWS managed policy affect every identity it is attached to. You cannot change the permissions in an AWS managed policy.

Assignment guidance

You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. The Amazon SQS Developer Guide says you can attach it to your Amazon SQS identities. It fits where read-only access to Amazon SQS is intended.

Same service

Same domain

Frequently asked questions

When should I attach AmazonSQSReadOnlyAccess?
The Amazon SQS Developer Guide says you can attach it to your Amazon SQS identities and that it grants read-only access to Amazon SQS. Attach it where viewing queues is the intended scope.
What does AmazonSQSReadOnlyAccess grant?
It allows sqs:GetQueueAttributes, sqs:GetQueueUrl, sqs:ListDeadLetterSourceQueues, sqs:ListQueues, sqs:ListMessageMoveTasks and sqs:ListQueueTags on all resources.
What are the security risks of AmazonSQSReadOnlyAccess?
It has no send, receive, delete or purge action, but it applies to all queues and lists their attributes and tags. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AmazonSQSReadOnlyAccess",
      "Effect": "Allow",
      "Action": [
        "sqs:GetQueueAttributes",
        "sqs:GetQueueUrl",
        "sqs:ListDeadLetterSourceQueues",
        "sqs:ListQueues",
        "sqs:ListMessageMoveTasks",
        "sqs:ListQueueTags"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v4, edited by AWS on 2024-05-24. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess

Terraform

resource "aws_iam_role_policy_attachment" "amazonsqsreadonlyaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonSQSReadOnlyAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonSQSReadOnlyAccess"),
);

Sources