1

I am trying to send an SQSMessage that is consumed from a SQSEvent.Records list explicitly to a DLQ. I understand that I can send it to the queue like any normal queue as long as the queueClient is pointing the DLQ.

The part I am having trouble with is that the SendMessageRequest object (which the queueClient publishes) only has a parameter for the string messageBody. I however have an SQSMessage object and would like to persist all the metadata as well. I feel if I just use the Body property of the SQSMessage object, all the metadata will be lost? (MessageId, EventSource, MessageAttributes) etc

Pbb
  • 408
  • 6
  • 21
  • You are correct. You can't preserve the metadata, unless you embed it in a body. – Marcin Dec 01 '22 at 04:25
  • What if you do not delete the message after the processing and set the Queue configuration (Maximum receives) to move message to DLQ after 1 receive. This will push to message to DLQ once the message is processed without you doing it manually. – Chetan Dec 01 '22 at 04:25
  • @Chetan there are some use cases where we want to keep the retry on the SQS level for messages. but for other use cases we want to directly publish to DLQ as we dont want to retry for thos cases – Pbb Dec 01 '22 at 04:28
  • @Marcin does the metadata get preserved when the message is sent to the DLQ through the SQS level (implicitly through maximum recieves)? i would assume so, but my familiarity is lacking – Pbb Dec 01 '22 at 04:30
  • Probably not, but you can test it easily. Setup some queue + DLQ and check how it works. – Marcin Dec 01 '22 at 04:31
  • `I am trying to send an SQSMessage that is consumed from a SQSEvent.Records list explicitly to a DLQ.` - why? – Ermiya Eskandary Dec 02 '22 at 15:40
  • @ErmiyaEskandary there are some use cases where we want to keep the retry on the SQS level for messages. but for other use cases we want to directly publish to DLQ as we dont want to retry for thos cases – Pbb Dec 02 '22 at 18:20

1 Answers1

0

You can use SQS+DLQ it won't change the metadata of the message. Also, if your case is just to delay the message why not use Visibility Timeout like 0 to make DLQ movement faster or say close to 12 hr to consume the message slower.

Ayush Singhal
  • 21
  • 1
  • 6