AWS Lambda now charges for INIT Phase
(aws.amazon.com)
from chaospatterns@lemmy.world to programming@programming.dev on 30 Apr 2025 05:59
https://lemmy.world/post/28897288
from chaospatterns@lemmy.world to programming@programming.dev on 30 Apr 2025 05:59
https://lemmy.world/post/28897288
Effective August 1, 2025, AWS will start billing for compute used during INIT phases. No more doing lots of work in your init phase for free
threaded - newest
This just means more people will set up Eventbridge rules to call lambdas regularly and keep them running. You avoid having to pay the time penalty and now, actual financial cost of a cold start.
Ah yes, keeping your Lambda functions running, rendering the main benefit of them pointless 🙃
People really should just set up a Fargate task instead…
Yeah I often see devs come up with complex architectures to just work around Lambda’s limitations. Things to keep them warm (but then fail because they don’t account for concurrent requests still hitting cold starts), multiple levels of Lambda functions to work around 15 minute time outs, and more. Just use the right tool for the job and look at Fargate or Batch.
Since AWS controls when the function is expired from warm start to cold start, it’s a guarantee they’re going to become extra aggressive about terminating idle functions.
Why leave customer code loaded for free when you can charge for startup again?
That’s an inherent problem with serverless/functions as a service. There’s no guarantee at all on it staying warm for a given amount of time and any system that depended on it without paying for provisioned concurrency was just depending on hopes and dreams.
Cpuflation