AmazonSQSFullAccess
Summary
Provides full access to Amazon SQS via the AWS Management Console. The Amazon SQS Developer Guide says it grants permissions that allow full 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/AmazonSQSFullAccess- Default version
- v1
- Created
- Last edited
- Services
- sqs
Control-plane actions (20)
By access level: 3 Permissions management, 7 Read, 2 Tagging, 8 Write.
| Service | Granted | Access levels and limits | Granted by |
|---|---|---|---|
| SQS | All 20 actions (see the SQS page) | 3 Permissions management, 7 Read, 2 Tagging, 8 Write; 0 restricted, 0 conditional | sqs:* |
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 at least 80% of the write and permissions-management actions of: sqs (11 of 11).
Guidance
Practical scope
The policy is a single statement that allows sqs:* on Resource "*". It has no actions for other services.
Use cases
- Give users, groups or roles full 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
- sqs:* allows every Amazon SQS action on all resources.
- You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.
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 full access to Amazon SQS is intended.
Related policies
Same service
- AmazonEC2RoleforDataPipelineRole
- AmazonElasticMapReduceforEC2Role
- AmazonSageMakerGroundTruthExecution
- AmazonSageMakerPipelinesIntegrations
- AmazonSecurityLakeMetastoreManager
- AmazonSecurityLakePermissionsBoundary
- AmazonSQSReadOnlyAccess
- AutoScalingNotificationAccessRole
Same domain
Frequently asked questions
- When should I attach AmazonSQSFullAccess?
- The Amazon SQS Developer Guide says you can attach it to your Amazon SQS identities and that it grants full access to Amazon SQS. Attach it where that is the intended scope.
- What does AmazonSQSFullAccess grant?
- It allows sqs:* on Resource "*", which is every Amazon SQS action on all resources, and nothing for other services.
- What are the security risks of AmazonSQSFullAccess?
- sqs:* allows every Amazon SQS action on all resources. 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
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"sqs:*"
],
"Effect": "Allow",
"Resource": "*"
}
]
}
Version history
Current version v1, edited by AWS on 2015-02-06. 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/AmazonSQSFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonSQSFullAccessCloudFormation
Resources:
ExampleRole:
Type: AWS::IAM::Role
Properties:
AssumeRolePolicyDocument: {} # replace with your trust policy
ManagedPolicyArns:
- arn:aws:iam::aws:policy/AmazonSQSFullAccessTerraform
resource "aws_iam_role_policy_attachment" "amazonsqsfullaccess" {
role = aws_iam_role.example.name
policy_arn = "arn:aws:iam::aws:policy/AmazonSQSFullAccess"
}CDK (TypeScript)
role.addManagedPolicy(
iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonSQSFullAccess"),
);Sources
- AmazonSQSFullAccess (AWS Managed Policy Reference Guide) (retrieved ; supports summary, practicalScope, securityConsiderations, assignmentGuidance, faqs)
- AWS managed policies for Amazon SQS (Amazon SQS Developer Guide) (retrieved ; supports summary, useCases, assignmentGuidance, faqs)
- AWS managed policies for job functions (IAM User Guide) (retrieved ; supports bestPractices, faqs)
- Managed policies and inline policies (IAM User Guide) (retrieved ; supports securityConsiderations, faqs)