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.
GoKawiil's interpretation of the reporting above, not reported fact.
By removing the need for adapters or rewritten handlers, AWS appears to be lowering the barrier for developers to move existing web backends onto serverless infrastructure, which could broaden Lambda's appeal beyond typical event-driven workloads. Offering three complementary execution models under one operational framework suggests AWS wants Lambda to serve as a single platform spanning asynchronous processing, interactive web APIs, and sandboxed code execution.
- Lambda Web Functions let standard HTTP servers run on Lambda without code changes or adapters.
- AWS now offers three Lambda form factors: Event Functions, Web Functions, and MicroVMs.
- Web Functions use active CPU billing and support multi-concurrent request handling, unlike the original event-driven model.
Source: aws.amazon.com, 2026-10-13
Published there as: “AWS Lambda Web Functions”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.