Issue with number of lambda functions in Serverless
See original GitHub issueHello.
I had strange issue with quantity of lablda functions:
Error --------------------------------------------------
The CloudFormation template is invalid: Template format error: Number of resources, 208, is greater than maximum allowed, 200
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Someone has in idea how I can handle this out.
_Note* If I comment out several functions from yml file its starts to deploy so its for sure with count of functions that I have. _
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
What's the big problem with having a large number of Lambda ...
To finish on this point, in my experience having hundreds of Lambda functions is not a significant overhead at deploy time as existing...
Read more >AWS Lambda Functions - Serverless Framework
All of the Lambda functions in your serverless service can be found in serverless.yml under the functions property. ... The handler property points...
Read more >Issues to Avoid When Implementing Serverless Architecture ...
1. Using monolithic Lambda functions with a large code base · Break up large Lambda functions into smaller ones with less business logic...
Read more >Serverless Limitations with Lambda - CloudCasts
Laravel Vapor users run queue jobs using SQS, which invokes Lambda functions. That means that with Vapor, your queue jobs are limited to...
Read more >AWS Lambda Limits to Keep in Mind When Developing a ...
To resolve this issue, developers will need to write any files to the /tmp directory which is dedicated for data storage on AWS...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @pmuens
Hey @larrybek thanks for opening 👍.
Unfortunately this is a CloudFormation limitation. A possible solution would be to split up your large Service into multiple smaller ones.
If you want smth. more automatically you should look into this plugin: https://github.com/dougmoscrop/serverless-plugin-split-stacks
You can find more information about this here:
I’ll close this issue for now since it’s a duplicate of #3411 and #2387