Chalice: Multiple Lambdas in 1 Chalice project

[honzous]

Could we choose if we want to deploy 1 big function (current way) or to deploy separate functions for each routing definition? This could save resources and improve execution times for more robust projects.

[TronPaul]

It would also be helpful to be able to deploy non-chalice lambdas as well, ie custom authorization lambdas, during chalice deployment.

[frob]

I thought this could be done with endpoint variables? Take a look at the docs for addition routing

[jamesls]

It's now possible to deploy non-chalice lambda for custom authorizers as well as scheduled events, but we still use one lambda function for the API handler.

However, deploying as separate functions is going to be difficult at this point. There's some assumptions baked into chalice's deployment process that assumes there's one lambda function as the API handler.

I'm going to mark this as out of scope for now, but if people want this please feel free to comment/+1 the issue and share your use case.

[advaer]

+1. For now I use separate chalice apps to keep lambdas not so huge.

[luisdemarchi]

@advaer How do you maintain the same API gateway?

[gmachado-nextreason]

+1 separate lambdas

[eallais]

+1
Any updates?

[pdyba]

+1 for separate lambdas
Any updates?

[RahulChowdaryN]

+1 for configuring separate lambdas