Use of Rebus with "native" AWS messages? about rebus.amazonsqs HOT 2 CLOSED

Hmmm, my least favorite answer;-) But fair enough! It was kinda what I expected. I'll figure out another way...Thanks for the rapid feedback anyways!

from rebus.amazonsqs.

Yeah well, I can definitely see why this would be useful.

BUT Rebus requires the presence of the rbs2-msg-id header with the message's ID.

AND Rebus' SQS transport uses a special envelope for messages to cope with SQS' built-in limitation that messages can have no more than 10 headers.

So there's a couple of built-in obstacles that prevent you from using Rebus directly.

What you COULD do though, as you mention (and this would be my preferred solution), is to map the messages to something Rebus can work with in a Lambda function, or in a background thread in the process that hosts your Rebus endpoint.

from rebus.amazonsqs.