r/awslambda • u/Tobi_Dashbird • Jan 31 '22
r/awslambda • u/No_Examination_5345 • May 19 '21
How to run a health check on your AWS serverless environment with Stackoscope
r/awslambda • u/julianwood • Dec 01 '20
New for AWS Lambda – Container Image Support | Amazon Web Services
r/awslambda • u/svennanderson • Apr 18 '20
serverless redis
We saw so many people asking Redis for their serverless stack. Unfortunately all cloud providers serve Redis with `per instance/memory` model.
So we decided to solve this and started working. We have just launched lambda.store. It is `serverless redis as a service`. We have a free tier and then charge per request. Right now it is AWS only.
Waiting your feedback and questions
https://medium.com/@LambdaStore/serverless-redis-is-here-34c2fa335f24
r/awslambda • u/versaceblues • Dec 04 '22
Default Lambda development experience seems atrocious or am I missing something
So im currently working on setting up lambdas using sam and this seems like an absolutely awful development experience.
I like to frequently run my code as im developing it.
However it seems I need to run a sam build + sam invoke every-time I make a change. Normally im used to tools like hot-reloading upon making a change.
Sam build is taking 10-20s to compile all my dependencies. Even on a small test project.
Is this the recommend development workflow for lambdas... or it just for sanity checking builds at the end of a cycle. What do you recommend for a more lightweight dev experience.
r/awslambda • u/Dashbird • Apr 07 '21
Best practice for logging in AWS Lambda
We updated our guide on the best practices for logging AWS Lambda and thought we could use your input!
Some key points from the article:
You can put logging statements in your code to validate that your code is working correctly and as expected.
You need to be very careful about what you log and not forget to remove debugging log statements from your code when deploying to production.
Refactor your log statements for CI/CD.
Keep AWS’ egress traffic costs in mind. While it’s free to get data into AWS, you have to pay to get it out again.
You can also buy reserved concurrency for the log shipping function, which will limit its maximum number of simultaneous executions.
A more economical way to get your logs out of AWS would be to stream them from CloudWatch Logs to a Kinesis.
Avoid is the manual process of subscribing to log groups from your shipping function.
You can add another Lambda function that can automatically update the retention policy as to not keep them forever (and eating away at your costs).
Use observability services like Dashbird (😉) so you can monitor without extra costs, and without slowing down your app with extra requests.
How does your current logging process look like?
r/awslambda • u/doriaviram • Oct 25 '20
Lambda Execution Leaks: A Practical Guide
r/awslambda • u/robertofrontado • Oct 24 '20
Serverless: Simple CRUD Application in 10 minutes on AWS
r/awslambda • u/SergeBoroday • Nov 05 '19
Lambda Cold Starts resolved with Docker Checkpoints
A Master Student developed a techniques and Go prototype tool to combat cold starts. It dumps app state (RAM) using docker checkpoints. https://www.imperial.ac.uk/media/imperial-college/faculty-of-engineering/computing/public/1819-ug-projects/StenbomO-Refunction-Eliminating-Serverless-Cold-Starts-Through-Container-Reuse.pdf The techniques should be especially effective for Python and other scripting language that have low cold start time to start instance, but take a lot of time to load larger libraries and frameworks.
The current 'best practice' is to keep lambda warm with a periodic ping, which works fine if your app does not need support simultaneous requests, from different users or same page. One can try to monitor lambda and ping as many times as needed like lamdba-warmer package does, but it increases the fees accordingly. Checkpoints seems more promising solution.
r/awslambda • u/nlehman06 • Jun 27 '19
How I Made Power Outage Notifications Using a Serverless Function for Free
r/awslambda • u/Fantastic-Path-5025 • Dec 07 '25
Building a Serverless Ad Tracker: Scaling to Millions of Events and Back
r/awslambda • u/soonth • Jun 09 '23
tinymo - an npm package making DynamoDB CRUD operations easier
r/awslambda • u/jointleman • Aug 18 '22
Lambda duration is scaling with the amount of times I invoke it in parallel. Any ideas why?
Hey there, I'm not expecting a concrete answer but any ideas on why this is happening are welcome.
Objective: I'm testing the performance of one of my services. Wanted to benchmark how well it worked for different load capacities.
The service: It's a an AWS/lambda that loads data from a PostgreSQL database, performs some complex tasks and than writes to the database by the end.
Lambda Config: It's deployed with serverless, with a `maxConcurrency:240` and a `memorySize: 2048MB` which means the CPU has 2 cores.
Testing setup:
I created a simple script that creates a bunch of threads and starts them at the same time, each thread will invoke the lambda with the exact same parameters and wait for it to finish (`InvocationType='RequestResponse'`). I then measure how much time it takes between the invocation until the last lambda finishes execution.
I performed this experiment with several load capacities (in this context, more load simply means that i call the lambda more times), and several times for each load amount (10 to be exact - to make sure the results are consistent).
Results (unexpected behavior):
The results are displayed in the boxplot bellow (latency in seconds):

I can understand the duration being higher with 480 invocations since the max concurrency is at 240, but shouldn't all the other results be somewhere around the same duration? I've investigated further to ensure this wasn't a measuring error and I'm absolutely sure that the amount of times I invoke the lambda is influencing its duration.
I'm starting to think that this might be related with database accesses, but even so I checked and the maximum amount of connections of my database is set to 100 so it still doesn't justify some of these unexpected results.
I'm really running out of ideas for how I can identify and hopefully fix this scalability bottleneck, any ideas are welcome.
Thank you in advance!
r/awslambda • u/[deleted] • Aug 09 '22
AWS Announced Tiered Pricing for Its Serverless Offering Lambda
r/awslambda • u/camus-py • Apr 17 '22
AWS Step Functions Workflow - AWS SAM example
r/awslambda • u/unlocknode • Feb 18 '22
Using AWS Lambda and Golang to access real-time weather station data
r/awslambda • u/Dashbird • Jan 07 '21
Deploying AWS Lambda with Docker Containers: I Gave it a Try and Here’s My Review
As everyone knows, AWS Lambda now supports Docker Containers. We tried it out and wrote a little review while we were at it (with ETL examples). You can read it here: https://dashbird.io/blog/deploying-aws-lambda-with-docker/
r/awslambda • u/binaryfor • Dec 31 '20