Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

66%
+2 −0
Q&A Access denied to read SQS queue just created

I've been trying to get Amazon SQS working with the v3 JS client. I've gotten to the point where I can successfully create a queue using the frontend, but the issue starts when I try and send/recei...

1 answer  ·  posted 2y ago by Darvids0n‭  ·  last activity 2y ago by Darvids0n‭

#1: Initial revision by user avatar Darvids0n‭ · 2022-04-21T05:46:52Z (over 2 years ago)
Access denied to read SQS queue just created
I've been trying to get Amazon SQS working with the v3 JS client. I've gotten to the point where I can successfully create a queue using the frontend, but the issue starts when I try and send/receive on that queue.

The exception I'm seeing is:
```
Access to the resource https://sqs.<region>.amazonaws.com/ is denied.
```

Here is essentially what the code is:
```
  this.sqs = new SQSClient({
	region: <region>,
	credentials: this.creds
  });
  const createQueue = new CreateQueueCommand({
	QueueName: `myqueue.fifo`,
	Attributes: {
	  FifoQueue: 'true',
	  ContentBasedDeduplication: 'true'
	},
	tags: this.amazonService.getResourceTags()
  })
  const queueUrlJson = await this.sqs.send(createQueue);

  const receiveMessages = new ReceiveMessageCommand({
	MaxNumberOfMessages: 10,
	QueueUrl: queueUrlJson.QueueUrl,
	VisibilityTimeout: 5,
	WaitTimeSeconds: 5
  });
  const messages = await this.sqs.send(receiveMessages);
```

The `createQueue` command succeeds, but the `receiveMessages` command fails. The relevant IAM policy has a wildcard on `sqs:*` with restrictions related to `aws:ResourceTags`. I'm confused as to why one operation is allowed, which would mean the tags matched, while the other is denied.