Please vote on this issue by adding a š reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
I am using SNS to deliver messages to App Runner. When App Runner reaches the concurrency limit it will return a number of 429 responses until the new container spins up to handle the traffic. SNS seems to treat all non-5xx responses as successful, so it does not try to re-deliver the message according to a retry policy, or put the message in a configured DLQ. Therefore, the message is lost.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I have considered using SQS, but I prefer push messaging as much as possible. I think this (SNS to App Runner) is a valid use case for SNS since it is advertised as supporting application to application messaging.
Additional context
Anything else we should know?
If this is a wontfix because 429 is the correct response code (fair point), can someone get a hold of the SNS team and see if they can make a feature to allow an SNS subscription to treat 429 the same as it does for 5xx?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Community Note
Tell us about your request What do you want us to build?
I am using SNS to deliver messages to App Runner. When App Runner reaches the concurrency limit it will return a number of 429 responses until the new container spins up to handle the traffic. SNS seems to treat all non-5xx responses as successful, so it does not try to re-deliver the message according to a retry policy, or put the message in a configured DLQ. Therefore, the message is lost.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
I have considered using SQS, but I prefer push messaging as much as possible. I think this (SNS to App Runner) is a valid use case for SNS since it is advertised as supporting application to application messaging.
Additional context Anything else we should know?
If this is a wontfix because 429 is the correct response code (fair point), can someone get a hold of the SNS team and see if they can make a feature to allow an SNS subscription to treat 429 the same as it does for 5xx?
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)