|
|
|
|
|
|
by TruffleMuffin
1970 days ago
|
|
|
This is a fantastic feature. Perfect for a use case I have currently which I built a custom Lambda function to execute. The one missing piece is that I don't see any way at the moment on how to deal with queue message attributes. I use these to contain critical meta data across messages of different types with with cross cutting information. For example. "A tenant identifier" for a multi-tenant scenario. That data is lost with a pure subscription as I understand it. |
|
|