🆕 What to DO when a MESSAGE FAILS PROCESSING? SQS Dead Letter Queues and SQS DLQ redrive

[@foobar_codes]

Thanks for watching this video. You can learn more about EDA in this playlist: th-cam.com/play/PLGyRwGktEFqd5PqaDPuLgFtVgtTFB-wGC.html

[@cristianpopescu119]

Thank you for the amazing content and for blowing my speakers up at the beginning :D

[@gerardopuchetafigueroa4705]

Thanks for the hands-on explanation.

[@foobar_codes]

Thanks for watching ☀️

[@elClubdelas7Cifras]

entonces
si algo falla en la lambda
se registrará en la dlq
se acumulará ahí por 4 días , ese behavior es default
me da 4 días para revisar los errores y con eso ejectutar el redrive para no perder dichos eventos
podría agregar una notificacion con cloudwatch alarms notificando si hay desde 1 error para estar enterado
Con este sistema no pierdo los eventos
lo qe salga con error por alguna razón, al menos se guardan y peuden volver a ser procesados

[@JuliaLopez-n8r]

Hola Marcia!! muchisimas gracias por el video, me sirvio mucho. Muy buen contenido!
Te hago una observacion constructiva: "q" se pronuncia /kiu/ en ingles, o sea sqs = /es-kiu-es/ , que tiene mas sentido porque queue se pronuncia /kiu/, entonces tiene como ese sentido de las siglas pero tambien como alusion a la cola.
Por otro lado queria consultarte porque me pasa que usamos colas FIFO y que cuando hay mensajes que no se pueden procesar, se tranca la cola y se nos acumulan mensajes. Eso hace saltar mil alarmas y trancar el resto de los mensajes que capaz no tienen error. Asi que creo que la dead letter queue nos puede ayudar a seguir procesando mensajes hasta que podemos resolver el root cause.
Gracias!

[@jigarthakkar5518]

Hello Marcia
Thanks for this video.
Can you guide on my below use case.
I have configured event bridge with sqs and dead letter queue.
I need a solution where assumed worst case that event bride is failed to deliver a record to api destination due to any 4xx error
So the records will be there in deadletter queue correct?
In such case how do I automate this scenario where i should know about this problem on right time and trigger should be generated which will ptocess all records from dead letter queue to send back to sqs and then event bridge.
Thank you

[@AshishYadav-sb4lh]

Hello Marcia ,
Thanks for the informative AWS videos.
I have one doubt. Does these DLQ re-drive works automatically once configured?
I means once failed messages are pushed to DLQ by source SQS , then we go to DLQ and click on button start DLQ redrive.
But instead of clicking the button , will this feature support automatic redrive meaning sending message back to source queue after certain time intervals.
is this manual process only ?

[@diegocoding]

Thanks! it was very useful

[@michaelmenard8614]

awesome as always.

[@foobar_codes]

Thanks again!

[@naveenpathiyil7151]

Great tutorial 👌👌

[@foobar_codes]

Thanks

[@naveenpathiyil7151]

@@foobar_codes Can we enable auto retry of the messages(lets say 3-4 times) from the DLQ without manually going to Console and doing It ?

[@arunwork001work8]

Hi, Is it possible to invoke DLQ redrive Automatically when ever there is an message in DLQ.

[@foobar_codes]

I dont see an api or command in cli for this :(

[@abhaythakur8572]

is there any config to redrive message without using aws console

[@foobar_codes]

I dont see an api or command in cli for this :(

[@zoladkow]

i know it's just me, but i find that too much gesturing makes the narrative hard to follow 😑