- Le plus récent
- Le plus de votes
- La plupart des commentaires
Could it be that you have another consumer on that queue that consumes the messages before you get them in your app? Check the queue metrics, specifically, NumberOfMessagesSent. This will let you know if any messages were added to the queue.
Are you seeing an error messages or is your code throwing exceptions when you are sending messages? Have the IAM permissions changed so that you (and/or the code/Lambda function) are no longer allowed to send messages to the queue?
It looks like you're doing all the right steps. If it were me, I'd delete and recreate the queue as well.
No errors shown in AWS console or from the application. Updated original post with timeout error given by Lambda.
I don't think any IAM permissions changed but even if they did, as a user with full admin privileges, shouldn't SQS be able to send a message to itself from the AWS console?
If the queue was (somehow) deleted/recreated you would be seeing the Lambda fail because the permissions have to be re-established but sending would still work. Other consumers would (probably) continue to work. As per Uri's comment I would definitely raise a support case here to track where the messages are going.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 5 mois
- demandé il y a 13 jours
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an
Unless someone created another instance of the environment and connected to the queues, I don't think it's likely there is another consumer.
I checked the queue metrics. It looks like no messages have been sent to the queue since Wednesday, which coincidentally is the last day I saw things working. I also tried sending a message now and could not verify in any way that the message was sent or received.
I would suggest creating a support case.
How do I create a support case?
"Technical support is unavailable under the Basic Support plan. Upgrade your plan to gain access to AWS technical support, architectural guidance, and more."
So is there no way to get help on this without paying for a support plan?
Here on the forums we don't have access to your details; nor do we have the same access that the support team does to support you. We can only give general advice because we cannot see how the underlying services are configured.