From 0 to now knowing what Deadletter Queues are and how to set up in AWS Thanks!
@Atul_Shegokar2 жыл бұрын
Thank you Man. I liked your attitude & way of explaining.
@camiloportilla-z7f10 ай бұрын
thanks for the video, very useful
@arkster002 жыл бұрын
There's a bit more involvement here. You can set the retry on the queue level but theoretically that will clash with the # of retries you have on the lambda. So setting the sqs queue retry to 0 helps. Also you need to understand what visibility timeouts are and how they are set for threads that access the message in the queue. The reason you couldn't see the message when you were refreshing was that that timeout had not yet expired before that message was re-placed back into the queue (regular not dlq). The idea and goal is that when the lambda exhausts all the retries and still fails, then the message is then moved to the DLQ. There are configurations on how long the message can stay in the DLQ or regular queue.
@SoumilShah2 жыл бұрын
Thanks a lot for those comments yes you are right and i forgot while i was creating video thanks a lot for posting this
@janivimal2 жыл бұрын
Soumil, well explained !! Question : messages that went to dlq , went through sqs-dlq or lambda dlq ? is it mandatory to configure dlq on both lambda and sqs ? or either one would work ?
@SoumilShah2 жыл бұрын
No just configure on sqs side that’s it
@janivimal2 жыл бұрын
@@SoumilShah Thank you !
@vipinreddy90533 жыл бұрын
Hey Soumil, I really appreciate your content. I have a request, can you post a video on a use case that basically runs a scheduled batch job on the files uploaded in an s3 bucket and scan them one by one and if no malware is found, the files are moved into a processed folder of another s3 bucket?
@ramchandgadde9 ай бұрын
change your solgan in queue to "Bro....Born to Win"😉