Why is my recreated DynamoDB trigger no longer firing my lambda function?

Question

It is unclear to me why the lambda-based trigger I just recreated atop my DynamoDB stream has stopped firing. Per the docs, I know that the stream atop my single sharded DynamoDB instance sends the payloads synchronously and will not invoke subsequent batches until the previous one finishes.

Because I wanted to recreate the trigger with more batches processed per payload (from 100 to 5000) I took these steps:

Deleted the trigger.
Disabled the previous dynamodb stream;
Re-enabled the stream (creating a new ARN with the updated timestamp);
Recreated the trigger tied to the same lambda (with a batch size of 5000).

Either the lambda that polls the stream and sends those batches to my lambda is not polling OR by doing one of the above steps, I've voided the stream and it has no new results. But I've since updated dynamodb directly as well as inserted new rows. The trigger still hasn't fired.

I'm not sure what I'm missing?

Please check the event source mapping of Lambda using aws lambda list-event-source-mappings --function-name myFunction — notionquest
– notionquest, Commented Feb 9, 2017 at 11:49
Also, have 5000 events accumulated or more than 24 hours passed? — Alexander Patrikalakis
– Alexander Patrikalakis, Commented Feb 13, 2017 at 0:47
@AlexanderPatrikalakis - when it has worked, i can see that the trigger fires whatever it accumulates events (up to 5k) as AWS uses an internal lambda to poll the dynamodb stream for events, then subsequently invokes my lambda with that payload - so neither waiting for 5k events or 24 hrs is a prerequisite here. — TimDog
– TimDog, Commented Feb 20, 2017 at 20:17
Please raise an issue in the AWS Lambda Forum so that AWS can review your usage. — Alexander Patrikalakis
– Alexander Patrikalakis, Commented Feb 21, 2017 at 3:37

Alexander Patrikalakis · Accepted Answer · 2017-02-13 00:54:21Z

0

Lambda functions may not execute for a variety of reasons.

Lack of permissions
Trigger not being enabled
DynamoDB Stream being disabled
Hitting Lambda region and account limits

answered Feb 13, 2017 at 0:54

Alexander Patrikalakis

5,2251 gold badge35 silver badges49 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why is my recreated DynamoDB trigger no longer firing my lambda function?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related