AWS announced Lambda Web Functions on October 12, 2026, saying it was available that day in five AWS Regions. The new Lambda form factor is designed for standard port-listening Node.js HTTP applications: a server reads its host and port from AWS_LAMBDA_HTTP_ENDPOINT and handles HTTP requests rather than being recast as a Lambda event handler.

How the HTTP model works

With Lambda Web Functions, the application runs as a web server that listens for requests on the host and port AWS provides through AWS_LAMBDA_HTTP_ENDPOINT. AWS names Express, Hono, Fastify and Next.js among the Node.js framework examples. The change is the execution model: the application can use a conventional HTTP server pattern instead of translating its request handling into Lambda-specific event handlers.

Launch runtime, concurrency and Regions

AWS specified Node.js 24 (nodejs24.x) on Arm64 at launch, with up to 128 concurrent requests per execution environment. AWS also said the service supported connectivity to a virtual private cloud (VPC), allowing an application to reach resources inside that VPC.

The five Regions AWS named were US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo) and Europe (Ireland).

AWS described billing by active CPU time, while memory is metered for as long as the execution environment exists. Those are separate usage meters: the CPU measure tracks active CPU time, while the memory measure follows the environment’s lifetime.

AWS’s deployment and traffic examples

AWS’s Express.js walkthrough uses aws lambda-web deploy; AWS reported that its first endpoint was created in under a minute. In a separate example, AWS deploys a function to us-east-1, eu-west-1 and ap-northeast-1, then uses a global URL for best-effort latency-based routing.

For a canary rollout—a gradual release that sends some traffic to a new version—AWS’s example directs 90% of endpoint traffic to an existing revision and 10% to a new one. AWS also describes using Amazon CloudFront to cache static content and route dynamic requests to a Web Function. With CloudFront origin access control (OAC), signed origin requests let the function endpoint restrict invocation to the associated distribution.

Where it fits among Lambda approaches

Lambda Web Functions is built around HTTP servers. AWS describes Lambda Event Functions as event-driven handlers, with single-request concurrency and wall-clock billing; it positions them for event processing and queue consumers. AWS describes Lambda MicroVMs as isolated, stateful sandboxes with customer-managed lifecycles, aimed at running untrusted or user-generated code.

AWS Lambda Web Adapter takes a different route: its project documentation describes an extension that connects HTTP applications to Lambda’s event-driven model and supports a broader range of languages and deployment approaches. Web Functions is AWS’s HTTP-native form factor, with Node.js 24 on Arm64 specified at launch. For a Node.js application already structured as a web server, that is the most direct distinction; the adapter is an alternative approach when its broader language options or extension-based model suit the application.