Why did my Amazon SQS messages get sent to a dead-letter queue?

[Music] [Applause] [Music] Hello, I'm Nishant, a cloud support engineer here at the AWS office in Bangalore. Today I'm going to show you how to troubleshoot why your Amazon simple Q service messages might have been sent to a dead letter Q. Let's get started. When you configure an Amazon SQS dead letter Q, messages are moved to this skew when the receive count for a message exceeds the max receive count value set for the source Q. The max receive count determines the maximum number of times that a consumer can receive a message from the source Q before being moved to the dead letter Q. To check the max receive count value for your queue, open the Amazon SQS console. Select the queue that you want to check and select edit. Under the dead letter Q section, the max receive count value is shown on the Amazon SQS console. This value is shown under the field maximum receives. The default is 10, but you can modify this based on your requirements. It's important to make sure that the max receive count value is set high enough to allow for sufficient receive attempts from Amazon SQS before messages are moved to the dead letter Q. Additionally, make sure that the dead letter Q has a longer retention period than the source Q. This gives you more time to process messages that end up in the dead letter queue before they permanently deleted. If you're using AWS Lambda to process messages from this queue, then you might need additional configuration to prevent valid messages from being sent to the Delta Q. Check the why is my Lambda function retrying valid messages knowledge center article for more details. Another potential cause is if you view messages in the Amazon SQS console. This counts against the red policy and can cause messages to be sent to the dead letter Q prematurely. To mitigate this, increase the maximum receive setting. Finally, be sure to delete messages within the configured visibility timeout window. messages received become visible again in the queue if they aren't deleted within the visibility timeout window. In summary, check the max receive count value, Lambda configuration if applicable, console message viewing, and prompt deletion of source Q messages to avoid unexpected dead lettering. And now you know how to troubleshoot why your Amazon SQS messages might have been sent to a dead letter queue. Thank you for watching and happy cloud computing from all of us here at AWS. [Music] [Applause] [Music]