AWS SQS issue. The specified queue does not exist for this wsdl version
Asked Answered
S

1

12

I'm facing the following issue.

My application wants to use two AWS SQS queues which are in the same region. My Applications running on EC2.

  • is there problem to have two AWS SQS queues in the same user & same region ?
  • When i try to connect from EC2 then it says "com.amazonaws.services.sqs.model.QueueDoesNotExistException: The specified queue does not exist for this wsdl version. (Service: AmazonSQS; Status Code: 400; Error Code: AWS.SimpleQueueService.NonExistentQueue; Request ID: e10c43db-e5db-5143-9"
  • I did try to connect with the same credentials from local environemt. It was able to connect and push the messages to the Queue.
  • My AWS User has SQS Full Access, even though it says Queue doesn't exist.

Thanks

Shiver answered 19/1, 2020 at 15:20 Comment(6)
In case you haven't figured it out, please double-check that the account number, the region, and the queue name (case-sensitive) are exactly what they are supposed to be. The case-sensitivity is where I always seem to have a problem.Airship
Thanks. Code is working after restarted the pods.Shiver
Related: github.com/localstack/localstack/issues/2843Mckinnon
If you are trying to delete a message using a ReceiptHandle of a non existent message, you will receive this error too. Very ConfusingSymmetrical
Also make sure that the RegionEndPoint you specify for the client object in your code is correct and is the same that you have coded in the URL.Guarantor
You might look at this answer once: - https://mcmap.net/q/340160/-quot-queue-does-not-exist-quot-when-accessing-my-sqs-queueCenter
H
0

According to the original poster in the comments above:

"Code is working after restarted the pods."

Hedley answered 7/12, 2022 at 9:41 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.