Lambda Web Functions

AWS Lambda Web Functions bill memory for minutes after requests finish, Easel finds

Easel tested AWS's newly announced Lambda Web Functions and found that execution environments kept running and accruing memory charges for 5 to 7 minutes after handling their last request, with no configurable idle timeout available. The company measured idle periods of 313 to 411 seconds across six environments, and found memory accounted for about 88% of total compute and request costs in its tests. Easel ultimately decided to run its own compute infrastructure instead, reporting it was also faster.

easel.sh · 2026-11-12

AWS launches Lambda Web Functions for standard HTTP apps

AWS introduced Lambda Web Functions, a new deployment option that runs standard port-listening HTTP servers built with frameworks like Express, Hono, Fastify or Next.js directly on Lambda, without requiring code to be rewritten as an event handler. AWS also renamed its original Lambda model 'Event Functions' and positioned both alongside Lambda MicroVMs, isolated sandbox environments for running untrusted code, as three distinct Lambda form factors sharing the same Firecracker isolation technology.

aws.amazon.com · 2026-10-13