AWS Lambda Web Functions run your Express or Next.js app as-is, billed on CPU time

AWS has added a third Lambda form factor aimed squarely at user-facing web apps. Lambda Web Functions run an ordinary HTTP server — Express, Hono, Fastify or Next.js — directly, with no event-handler rewrite and no adapter layer. One command, aws lambda-web deploy, returns a live HTTPS URL. Each execution environment serves up to 128 concurrent requests, and billing meters CPU time actually used rather than wall-clock time, which favours workloads that mostly wait: server-side rendering, API backends and token-streaming inference. Adding --regions replicates the code and puts latency-based routing behind a single global URL, and traffic can be split by weight across revisions for canary rollouts. At launch it covers five Regions, Node.js 24 on Arm64 with VPC connectivity, and CloudFront can use the endpoint as an origin. Lambda now spans Event Functions, Web Functions and MicroVMs on the same Firecracker isolation — worth a look for teams running small Node services on containers or Fargate.

This is a summary by our content curator. Read the original at AWS News Blog: https://aws.amazon.com/blogs/aws/announcing-aws-lambda-web-functions-for-fast-consistent-web-app-performance-anywhere/.