Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

unable to access sqs queue from ecs task

Open
#6 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws

Research direction

Start with the ECS role configuration referenced in the issue and reproduce the aws sqs receive-message command inside the container. Trace which role the task uses and compare its permissions with the named queue; done means identifying the cause of the denial and documenting or correcting the example so the task can receive messages.

Written by the indexing model from the issue text.

Description

I'm trying to understand how this worked. When I run it i'm able to create the SQS task and launch the task but when the ECS task tries to read from the queue it gets the following error, which I have reproduced by logging into the shell script container (after preventing it from exiting):

root@f9910bdcd9d6:/# aws sqs receive-message --queue-url=https://queue.amazonaws.com/831754492748/ecs-test-plepeskaQueue --region=us-east-1

An error occurred (AccessDenied) when calling the ReceiveMessage operation: Access to the resource https://queue.amazonaws.com/ is denied.

And this makes sense b/c although I can see that the ecsInstanceRole has a policy that gives it access to the S3 bucket I can't see where it is given access to the SQS queue.

Has something changed since this worked? Or, is there another reason why access to the queue is denied?

Dominant language
POV-Ray SDL
Stars
293
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/lambda-ecs-worker-pattern

All issues in aws-samples/lambda-ecs-worker-pattern

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.