You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingduplicateThis issue or pull request already exists
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.
The text was updated successfully, but these errors were encountered: