Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 8
    Your comment is the only one clearly explaining how SNS and SQS can be combined. Thanks! Commented Oct 19, 2020 at 11:06
  • I am a newbie to AWS, but has 3. changed since the answer was written? [docs.aws.amazon.com/sns/latest/dg/… Delivery Retries) Amazon SNS defines a delivery policy for each delivery protocol. The delivery policy defines how Amazon SNS retries the delivery of messages when server-side errors occur (when the system that hosts the subscribed endpoint becomes unavailable). When the delivery policy is exhausted, Amazon SNS stops retrying the delivery and discards the message—unless a dead-letter queue is attached to the subscription. Commented Mar 22, 2021 at 9:05
  • @buzztr 3. hasn't changed; it refers to the consumer of the SQS becoming unavailable. That documentation you cite describes a new feature of SNS in which failure to deliver a message to the consumer(s) (in this case, the SQS) after exhausting your retries results in SNS putting that message put onto a dedicated SQS queue for to handle transmission error. This means instead of the message being lost entirely, you have it saved and can re-attempt transmission through the SNS topic at a later date. Commented May 24, 2021 at 1:37