Grant AWS Lambda Access to an SQS Queue


Borislav Hadzhiev

Tue Sep 28 20213 min read

Grant AWS Lambda Access to an SQS Queue #

In order to grant a Lambda function access to an SQS queue, we have to attach an IAM policy to the function's execution role. The policy should grant permissions for all the Actions the function needs to perform on the queue.

For example, the following policy grants permissions for the most commonly used sqs actions on a specific sqs queue.

The policy applies to a specific queue, therefore make sure to replace the YOUR_* placeholders in the Resource element with the real values.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sqs:SendMessage", "sqs:DeleteMessage", "sqs:ChangeMessageVisibility", "sqs:ReceiveMessage", "sqs:TagQueue", "sqs:UntagQueue", "sqs:PurgeQueue" ], "Resource": "arn:aws:sqs:YOUR_REGION:YOUR_ACCOUNT_NUMBER:YOUR_QUEUE_NAME" } ] }

The Resource element is simply the SQS queue's ARN. It should look something like: arn:aws:sqs:us-east-1:123456789:my-queue once the real values are in place.

The actions your lambda function needs to perform on the queue are use case dependent.

You could set "sqs:*" for the Action element in the policy to grant full sqs access to the lambda function. However, it's best practice to grant an entity the least permissions that get the job done.

You can view a full list of the sqs Actions in the SQS actions table.

There is a Description column, which explains what each action does.

To attach a policy to the lambda function's execution role, you have to:

  1. Open the AWS Lambda console and click on your function's name
  2. Click on the Configuration tab and then click Permissions

click on function role

  1. Click on the function's role
  2. Click on Attach policies and click the Add inline policy button

add inline policy

  1. In the JSON editor paste the following policy.
Replace the YOUR_* placeholders and adjust the Actions your lambda function needs to execute.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sqs:SendMessage", "sqs:DeleteMessage", "sqs:ChangeMessageVisibility", "sqs:ReceiveMessage", "sqs:TagQueue", "sqs:UntagQueue", "sqs:PurgeQueue" ], "Resource": "arn:aws:sqs:YOUR_REGION:YOUR_ACCOUNT_NUMBER:YOUR_QUEUE_NAME" } ] }
  1. Click Review Policy and give your policy a name, then click Create policy

At this point the lambda function's role has been extended with a policy that grants access to some SQS actions on a specific queue.

It can take up to a minute until the IAM changes have been propagated and the policy is in effect.

Invoke your lambda function and verify whether it has access to the SQS queue.

If your function is still unable to access the SQS queue, try to increase the function's timeout by a second in the AWS console or simply add an extra print statement in the code and click the Deploy button.

If your lambda function still does not have access to the queue, expand the IAM policy you added to the function's role and edit it to look like the policy below.

edit policy

Replace the YOUR_* placeholders with real values.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "sqs:*" ], "Resource": "arn:aws:sqs:YOUR_REGION:YOUR_ACCOUNT_NUMBER:YOUR_QUEUE_NAME" } ] }

The IAM policy above grants full access to an SQS queue. Your lambda function will be able to execute all SQS actions on the queue.

It's best practice to grant the least possible permissions, that enable you to get the job done, however the * symbol is useful when debugging.

After you've updated the policy, try to invoke your lambda function again, it should have permissions to execute any action on the SQS queue.

After you verify which actions your lambda needs to run, you can make the IAM policy less permissive.

Note that a policy statement with a Deny effect will always override any Allow statements.

Further Reading #

Join my newsletter

I'll send you 1 email a week with links to all of the articles I've written that week

Buy Me A Coffee