Open lesimoes opened 3 years ago
Yes, the lambda mode is broken atm, I've linked an issue with the details.
@mzahor, recently I used your ideia shared in that post to build my own solution. The main ideia is all yours and works very well with lambda.
Thank you for your post.
Ps.: If you want I can share my solution with you, just let me know.
@lesimoes Please share your solution
@funkel1989 I did create another package because my solution doen't use same approach (consumer).
Thanks all for creating solutions for this problem, it's been very helpful for me to understand the different options there are for sending and receiving large SQS messages.
I see @funkel1989 has since created Battle-Line-Productions/sqs-large-payload-nodejs which looks good for my use case since it separates the processing of the sent SQS message from the receiving, so I can wire it into an SQS-triggered lambda which delivers the message to the lambda.
Just thought I'd mention it here in case as seems somewhat related to this issue and may serve as an inspiration for this ticket and I see the above repo's author (@funkel1989) in the comments above. If you have any other relevant info Michael, please feel free to comment.
Hello, I tried use package with my lambda functions, for SqsProducer works fine, it send a payload json to S3 Bucket, but my problem is when I need to consume a message that was sent to S3. I tried like this example: https://github.com/aspecto-io/sns-sqs-big-payload/blob/HEAD/docs/usage-in-lambda.md
But never runs the handleMessage function and always returns undefined response. The transformMessageBody runs but with body param undefined too.
My function getMessage should return a message payload.
This is my entire message payload
I send the first object of array Records, like this.
I really believe that I missed something but I dont know where. Could you help me?
Thanks.