s3 events are guaranteed to happen atleast once (not only once)
wildcard paths
environmental variables (pattern for prod/beta)
tests /offline mode
LAMBDA integration mode
logging
cloudformation templates
trigger another lambda
limits
npm prune --production
Lambda and event-based
dsf
Here are the things you need to know when using the Serverless framework:
Cleanup
By default, Serverless won't cleanup after you. If you have a Continuous Deployment setup, you'll hit the 75gb Lambda storage limit suprisingly quickly.
The fix is pretty simple, just install the purge-plugin
npm install --save-dev serverless-prune-plugin
Add the plugin to your serverless.yml file:
plugins:
- serverless-prune-plugin
And then prune old versions during your deployments
10 Things you need to know about Serverless
Lambda and event-based dsf
Here are the things you need to know when using the Serverless framework:
Cleanup
By default, Serverless won't cleanup after you. If you have a Continuous Deployment setup, you'll hit the 75gb Lambda storage limit suprisingly quickly.
The fix is pretty simple, just install the purge-plugin
Add the plugin to your serverless.yml file:
And then prune old versions during your deployments
Serverless outputs as env variables:
https://github.com/serverless/serverless/issues/2240