Sumanth Varada
Reputation: 1190
AWS SQS issue. The specified queue does not exist for this wsdl version
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
Upvotes: 13
Views: 23306
Answers (1)
Eric Hammond
Reputation: 22407
According to the original poster in the comments above:
"Code is working after restarted the pods."
Upvotes: 0
Related Questions
- Spring Cloud - SQS - The specified queue does not exist for this wsdl version
- The specified queue does not exist - AWS.SimpleQueueService.NonExistentQueue with Spring-Boot
- Amazon SQS:: Got an error while trying to create queue: NoCredentialProviders: no valid providers in chain. Deprecated
- Unable to configure SQS queue notification in S3
- SQS Lambda Integration - Lambda does not process the queue message
- Property 'Queue' cannot be empty
- SQS ExpiredToken: The security token included in the request is expired status code: 403
- AWS-CLI - SQS List Queues
- AWS SQS: Delay making available a message that failed to process
- AWS.SimpleQueueService.NonExistentQueue Exception thrown when Accessing Existing SQS queue