Add dead letter queue to API stack, to limit retries #660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
suzuki-safie
requested review from
statefb,
wadabee and
Yukinobu-Mine
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
None
Description of changes:
When published API handler failed, message in SQS queue will remain in the queue and retry occurs every 30 minutes for 4 days (192 times). This can cause unwanted mass usage of foundation model.
This PR adds dead-letter-queue to the queue and limit max retry count to 1.
cdk/lib/api-publishment-stack.ts: Added a dead-letter queuechatQueueDLQwith a retention period of 14 days and configured the mainchatQueueto use this DLQ with a maximum receive count of 2 (one retry).By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.