Skip to content

SNS outbound error when fetching for SNSSignature Cert

1

Do we need to fetch SigningCertURL each time handling SNS webhook ?.

Yesterday, my service faced high traffic around 3k sendEmail requests/min to SES in around 10 minutes -> In general, this service will handle multiply 4 times Webhook from SNS (around 12k), I checked my log and found out that my service met Outbound error when try to fetch to get the SNSSignature Cert. I guess that is throttling from SNS due to just met that in high traffic.

Which is the best way to due with this?

  • Rate limit my webhook handling or just ignore these outbound error from SNS server ?
1 Answer
0

Hi Snail,

This question seems closely related to your earlier post about outbound errors when handling SNS webhooks. I’ve provided a detailed answer to that question here, which includes solutions like caching the signing certificate, optimizing validation, and scaling your architecture to handle high traffic. These recommendations apply to the traffic volumes you’ve described (12k webhooks/minute).

Feel free to check it out, and let me know if you have additional questions or need further clarification. 😊


Cheers,

Aaron ✨

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.