AWS NEW FEATURE UPDATE: SQS DLQs - Automate & Streamline With Brand New APIs

AWS NEW FEATURE UPDATE: SQS DLQs - Automate & Streamline With Brand New APIs
Welcome to the Pythoholic channel! In today's video, we explore the latest updates from Amazon Web Services (AWS) - newly released APIs for Amazon Simple Queue Service (SQS) to supercharge your Dead-Letter Queue (DLQ) management.
From understanding why we need a DLQ to delve into the importance of the 'Maximum receive count,' we leave no stone unturned. You'll learn how to automate moving messages between standard queues and DLQs, all in an attempt to make your experience with AWS SQS smoother and more efficient.
These new APIs are a game-changer for optimizing their AWS SQS implementation and workflow. Don't miss out on mastering these powerful tools, which could be just what you need to take your AWS game to the next level.
As always, don't forget to like, share, and subscribe to Pythoholic for more insightful AWS content and tech discussions. Enjoy the video!
New API Link: aws.amazon.com/blogs/aws/a-ne...
Latest AWS CLI Installer: docs.aws.amazon.com/cli/lates...
🎉AWS Certified Developer Associate Free Course:
tinyurl.com/dvac01
🎉AWS Solutions Architect Associate Certification 2021 Playlist:
tinyurl.com/y4lr8zu4
🎉 Slides on the channel are available here in the link below:
ko-fi.com/pythoholic
🎉 Pythoholic is Creating visual content for all tech and programming on KZbin!
You can support by buying a coffee ☕️ here -
ko-fi.com/pythoholic
🍀 If you wish to support me please choose the links below:
INSTAMOJO: instamojo.com/@pythoholic
PAYPAL: paypal.me/pythoholic
GADGETS I USE: www.amazon.in/shop/pythoholic
Learn Once. Never Forget
🍀 KZbinr @BePythoholic 🎲
🍀 ko-fi.com/pythoholic
🍀 buymeacoffee.com/Pythoholic
🍀 Podcast (Blabber Cloud) : tinyurl.com/Pythoholic
🎯 Click Below
🚨 KZbin -- tinyurl.com/PythoholicYT
Disclaimer: The content provided in the channel is not affiliated in any way to the organization. We provide information here on the channel based on the knowledge we have on the topic. We advise our viewers to please do their own research and read more about them from the source provided by the organization to get a better outlook on the topic that has been covered.
These videos are just to provide you a platform to learn, and there can be mistakes and we are always trying to improve based on your feedback. we recommend viewers have an open mind. Please support the channel to get more content like these in the future.
#AWS #Technology #Pythoholic

[@Pythoholic]

New API Link: aws.amazon.com/blogs/aws/a-new-set-of-apis-for-amazon-sqs-dead-letter-queue-redrive/ Latest AWS CLI Installer: docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html

[@Alltopics4u]

Your video quality and content is always good, Please add good quality mic for these face to face video.

[@Pythoholic]

Thanks Sandeep for the feedback. These are older video I have updated my setup for better experience. Thanks again

[@AshishYadav-sb4lh]

@Pythoholic this feature added few months back only... i am already using but just want to check.. does redrive policy work automatically or we need to set some trigger to move message back to the source queue?

[@Pythoholic]

Hey there! So, redrive policies in Amazon SQS work automatically. When you set a redrive policy on a source queue and specify a Dead Letter Queue (DLQ), Amazon SQS automatically sends messages that have exceeded the maximum receive count to the DLQ. There's no need to set up additional triggers. Once you set the redrive policy, it automatically takes care of moving the messages to the DLQ. However, with the new APIs, you can manually trigger the move of messages back to the source queue from the DLQ. Remember, setting up a DLQ with a redrive policy helps you isolate messages that can't be processed correctly for examination and debugging.

[@AshishYadav-sb4lh]

@Pythoholic thanks for quick response... Sorry i was not clear with my question... sending message to DLQ is automated based on message count... but sending message back to source Queue from DLQ is still manual approach.. or need to set some trigger to send it back. is this right?

[@Pythoholic]

Yes we are on the same page itself, Moving messages back from the DLQ to the source queue isn't automated within AWS SQS itself. This is where the new APIs come into play. They give you the ability to manually trigger the move of messages back to the source queue from the DLQ. So, while the process of sending messages to the DLQ based on the maximum receive count is automatic, moving them back to the source queue for reprocessing is a manual task that you can now do with these new APIs. This manual approach provides you with the flexibility to decide when and which messages you want to move back for reprocessing. I hope that clears up your question!