AWS Lambda Web Functions runs your Express app as-is
A new Lambda form factor accepts a standard HTTP server instead of an event handler, so Express, Fastify and Next.js apps deploy without a rewrite.
AWS launched Lambda Web Functions on 12 October, a new way to run Lambda that listens for requests on a port instead of invoking a handler per event. Point an existing Express, Fastify, Hono or Next.js server at it and it runs close to unchanged, reading its listening address from an environment variable rather than being restructured into Lambda’s event model.
The runtime is Node.js 24 on Arm64, available at launch in five regions: US East (N. Virginia and Ohio), US West (Oregon), Europe (Ireland) and Asia Pacific (Tokyo). Each execution environment now serves up to 128 concurrent requests rather than one per invocation, and billing switches to active CPU time, so a request waiting on a database query or an API call costs little. Deployment is a single CLI command, with automatic multi-region replication, latency-based routing and canary releases through revision-weight shifting.
const [host, port] = process.env.AWS_LAMBDA_HTTP_ENDPOINT.split(':');Why it matters: the usual reason teams avoid Lambda for a full web app is rewriting routes into handlers and losing the concurrency a normal server gets within one process. This removes both. If you already run Express or Next.js, you can point it at Lambda largely as it is and pick up multi-region routing without standing up that infrastructure yourself.
The caveat: launch regions are limited to five, and only Node.js 24 is supported so far, so check both before planning a migration.