2 Answers
- Newest
- Most votes
- Most comments
0
Please check the following recommendations in the AWS SQS documentation on how to best configure the SQS Queue. https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-queueconfig
0
Problems like this are usually because the message isn't really being deleted by your Lambda. Have you made sure your exception handling on AWS API calls is solid, and do you have logging for any situations where your message processing or deletion could fail? Depending on traffic you could for example be hitting AWS API request throtting occasionally so make sure your SDK, or you, have retries in place with exponential backoff.
Relevant content
- asked 2 years ago
- Accepted Answerasked 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago