# Process large file on multiple lambda

**URL:** <https://forum.serverless.com/t/process-large-file-on-multiple-lambda/3388>\
**Category:** Serverless Architectures\
**Tags:** aws\
**Created:** [December 27, 2017, 3:10pm UTC](https://forum.serverless.com/t/process-large-file-on-multiple-lambda/3388 "2017-12-27T15:10:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pau](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@Pau](https://forum.serverless.com/u/Pau)\
**Post date:** [December 27, 2017, 3:10pm UTC](https://forum.serverless.com/t/process-large-file-on-multiple-lambda/3388/1 "2017-12-27T15:10:58Z")

</div>

Hi guys,

We have a use cases like this :

On a form I upload an XLS with many lines (more than 50k) and chose wich config I want for processing this file (Config like lambda 1, lambda 2, step functions 1).

When each traitements is done we want to generate a new XLS with new data from our lambdas .

Today, we want to insert each lines from our XLS file on DynamoDB and trigger lambda functions when we have a new entrie on our dynamoDB but I don’t know if is the best way to do this ?

Thanks for you help 🙂

---

<div class="post-metadata">

**Author:** ![ahansson89](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/ahansson89/32/1166_2.png) [@ahansson89](https://forum.serverless.com/u/ahansson89)\
**Post date:** [December 28, 2017, 9:33am UTC](https://forum.serverless.com/t/process-large-file-on-multiple-lambda/3388/2 "2017-12-28T09:33:59Z")

</div>

I would let the front end submit each line to a temp DynamoDB table, then process each line with your different Lambdas

---

<div class="post-metadata">

**Author:** ![ahansson89](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/ahansson89/32/1166_2.png) [@ahansson89](https://forum.serverless.com/u/ahansson89)\
**Post date:** [December 29, 2017, 6:29pm UTC](https://forum.serverless.com/t/process-large-file-on-multiple-lambda/3388/3 "2017-12-29T18:29:51Z")

</div>

Actually I take that back. After thinking about how I would do it, I would do it with an ETL job and AWS Glue.

Good luck.
