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 25, 2022. It is now read-only.
Hi,
I'm seeing the following error in my kinesis fanout handler deployment:
'Record too large to be pushed to target 'reconnectToDEV' of type 'kinesis''
The system is setup to take a single record from a kinesis stream (batch size == 1) and push it to a different kinesis stream.
So the question is, how is a single record from a kinesis stream too big to put into a different kinesis stream?
I suspect there is an issue with how the fanout handler is calculating the max allowed size from this line:
https://github.com/aws-samples/aws-lambda-fanout/blob/master/fanout.js#L63
AWS Support suggested that I open up a github issue, ticket #6553563951
Thank you,
Joe Bowen
The text was updated successfully, but these errors were encountered: