--- title: Announcing AWS Lambda Web Functions | daily.dev description: AWS Lambda Web Functions is a new serverless form factor that runs standard HTTP web applications (Express, Hono, Fastify, Next.js, or any Node.js framework)... canonical: https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Announcing AWS Lambda Web Functions | daily.dev og:description: AWS Lambda Web Functions is a new serverless form factor that runs standard HTTP web applications (Express, Hono, Fastify, Next.js, or any Node.js framework)... og:url: https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw og:image: https://api.daily.dev/og/posts/vjdzg5FBW.png og:image:alt: Announcing AWS Lambda Web Functions og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Announcing AWS Lambda Web Functions **[AWS](https://daily.dev/sources/aws)** · 6 min read · 0 upvotes · 0 comments ## Summary AWS Lambda Web Functions is a new serverless form factor that runs standard HTTP web applications (Express, Hono, Fastify, Next.js, or any Node.js framework) natively without rewriting code into event handlers. It uses multi-concurrent execution (up to 128 concurrent requests per environment) and active CPU billing, where idle I/O wait time consumes little CPU. Deployment is a single CLI command that handles scaling, multi-region distribution with latency-based routing, and canary traffic shifting between revisions. It complements existing Lambda Event Functions (classic event-driven model) and new Lambda MicroVMs (isolated sandboxes for untrusted code). It integrates with CloudFront via origin access control for private-origin serving. Available at launch in five regions, running Node.js 24 on Arm64, with VPC connectivity support. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is AWS Lambda Web Functions and how is it different from regular Lambda functions? AWS Lambda Web Functions is a new Lambda form factor that runs standard port-listening HTTP servers, like Express, Hono, Fastify, or Next.js, without rewriting code into an event handler. Unlike classic Lambda (now called Event Functions), which uses single-concurrent execution with wall-clock billing, Web Functions support up to 128 concurrent requests per execution environment and bill based on active CPU time rather than wall-clock time. _Teams weighing serverless options for HTTP backends can track changes like this one on daily.dev._ ### How do I deploy a Node.js Express app to AWS Lambda Web Functions? Deploy an existing Express.js app unchanged with the command `aws lambda-web deploy --name my-web-app --code ./my-app`, which bundles the source, creates the Web Function, publishes a revision, attaches an endpoint, and returns a live HTTPS URL in under a minute. Locally, set the AWS_LAMBDA_HTTP_ENDPOINT environment variable to the host and port, for example 127.0.0.1:3000, to run the same code without Lambda-specific adapters. _Developers shipping serverless Node.js apps can follow deployment changes like this through daily.dev._ ### Which AWS regions and Node.js runtime does Lambda Web Functions support at launch? At launch, Lambda Web Functions is available in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland), running Node.js 24 (nodejs24.x) on Arm64 architecture. It also supports Amazon VPC connectivity so functions can reach resources inside a VPC. _Architects planning multi-region serverless rollouts can check platform availability details via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 100 comments across hackernews (as of 2026-10-13). **TL;DR:** Reaction is split between excitement that Lambda finally runs standard web frameworks without an adapter/event-handler shim, and skepticism that this is just catching up to Cloudflare Workers, Vercel Fluid Compute, Google Cloud Run, and Azure Container Apps, which already offer similar or better scale-to-zero and billing models. **Sentiment:** 25% positive · 40% mixed · 35% skeptical **The case for** - Removing the adapter/event-translation layer is seen as a real DX improvement for teams already running Express/Fastify/Hono on Lambda. - Several people note Lambda-style scaling is genuinely valuable for extremely bursty, unpredictable workloads where paying per-use beats running idle dedicated instances. - Some see it as a credible, technically solid response to Cloudflare Workers, praised for first-class CloudFront origin support and easy multi-region/canary deployment. **The pushback** - Many argue Cloud Run and Azure Container Apps already do scale-to-zero, concurrency control, and no-adapter deployment, making this feel late rather than novel. - Commenters criticize billing/pricing complexity versus Cloudflare Workers, noting you still pay for memory and data transfer, not just active CPU. - Node.js-only support (no Rust/Go/C++/Java/.NET) is called a major limitation that undercuts the pitch for greenfield, performance-sensitive services. - Several raise concerns about cold starts persisting after idle periods despite multi-concurrency, and uncertainty around how it compares to containers/ECS/Fargate. - A broader thread argues FaaS/Lambda architectures generally add operational complexity and fragmentation compared to simpler container or VM-based approaches. **By community** - hackernews (mixed): Discussion splits between enthusiasm for the adapter-free DX and broad skepticism that this just replicates what Cloud Run, Azure Container Apps, and Cloudflare Workers already offer, with a long side-debate on FaaS tradeoffs in general. **Hottest debate:** Whether Lambda's new scaling/concurrency model is a genuine technical advance or simply replicates (with worse pricing/flexibility) what Cloud Run and Azure Container Apps have offered for years. **Open questions** - Will cold starts still occur after idle periods despite multi-concurrency and proactive scale-up? - Is this built on Firecracker microVMs or containers/WASM, and how does that affect startup times versus Cloudflare's V8 isolates? - Will support expand beyond Node.js to Python, Rust, Java, or .NET? - Can it be combined with SnapStart or container-based Lambda deployments for faster cold starts? **Highlights** > My biased take as the architect of Workers: It's a classic Clay Christensen innovator's dilemma. V8 isolates seem "worse" on their face (e.g. mostly incompatible with non-JS apps, more difficult to secure), while aiming down-market. The hyperscalers' biggest existing customers aren't asking for them; they are asking for more and better micro VMs to run their existing codebases. It's only the little guys looking to deploy greenfield apps with low ops overhead and on a tight budget that really appreciate the Workers model, and to AWS these seem like small potatoes. Meanwhile there's a huge amount of investment needed to build out this entirely new and different way of doing things (we've been working on it almost a decade now!). In the worst case, this investment is wasted, and in the best case, cannibalizes the existing product line. There likely many people at AWS who recognize the dilemma, but still cannot push the organization in the right direction. Too much inertia, too many stakeholders who don't get it, because it's unintuitive. When orgs get big they just cannot take disruptive steps, even when they were built on disruption in the past. They only finally come around after the new disruptor is eating their lunch, but by then it's too late. > — [kentonv on hackernews](https://news.ycombinator.com/item?id=50072261) > They're also good for extremely bursty loads. I use Lambdas extensively for a radar imagery API that delivers the images for an Android live wallpaper that shows weather radar. That particular use case can go from hardly any traffic at all to a hurricane of traffic during something like, well, a hurricane. For consistent processing loads, I think I could save money by just running on dedicated EC2 instances, but you cannot beat the instant scale of Lambdas. Shameless plug: https://play.google.com/store/apps/details?id=app.radarlove.... > — [ryandvm on hackernews · 2 comments](https://news.ycombinator.com/item?id=50071278) > I strongly recommend never using functions as a service unless you genuinely have some client edge compute requirement that absolutely cannot be solved via some other means. Everything about running software is made more difficult this way. You might think it would make certain infrastructure aspects easier, but it just changes the semantics of the same problem. It's the same quantity of mess to clean up, but now it's in these really weird piles that are often much harder to access. > up to 128 concurrent requests per environment I am fairly confident I could support more capacity with a single t3a.nano instance. > — [bob1029 on hackernews · 8 comments](https://news.ycombinator.com/item?id=50070068) > I would agree with OP with "stay away". The Google paper Towards Modern Development of Cloud Applications[0] does a great job explaining why. TL;DR the case they make against micro-services architectures (which Lambda encourages): 1. It hurts performance 2. It hurts correctness 3. It is hard to manage 4. It freezes APIs 5. It slows down application development For even a moderately complex system, spreading logic out over multiple discrete runtimes doesn't make sense; instantly run into each of the 5 points. The only times I've found functions useful is truly single-point behavior where we were running some logic connected to CloudFront on each request for some header parsing. It is certainly possible to write a monolith in Lambda as well, but then that would be bad architecture and a bad fit and I suppose why they are now introducing this new model that is more like GCP Cloud Run or Azure Container Apps. [0] https://sigops.org/s/conferences/hotos/2023/papers/ghemawat.... > — [CharlieDigital on hackernews](https://news.ycombinator.com/item?id=50071635) > Disappointed by the NodeJS-only requirement and the 128 req/env/sec ceiling. NodeJS-only feels very pre-AI. Let me tell my agent to write my web service in Rust/C++/C/Go/Zig, and ship a statically-linked single binary that fits within a maximum binary size ceiling. I'd get much better performance, and make much more of the premium CPU/RAM pricing that I'm being asked to pay in exchange for scale-to-zero and fast autoscaling. The rest is amazing. First-class support as a CloudFront origin. Easy multi-region and gradual deployment. Clearly, finally, a great response to Cloudflare. Just.... so close, and yet, so far. No way am I going back to Node as a web backend for greenfield projects in 2026. > — [solatic on hackernews · 1 comments](https://news.ycombinator.com/item?id=50077138) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50064063) · 16 points · 4 comments - [hackernews](https://news.ycombinator.com/item?id=50069318) · 81 points · 96 comments ## Similar posts on daily.dev - [You’re Paying for Servers You’re Not Using. AWS Lambda Fixes That.](https://daily.dev/posts/you-re-paying-for-servers-you-re-not-using-aws-lambda-fixes-that--pbzq6ixun) · Medium · 0 upvotes · 0 comments - [AWS Lambda](https://daily.dev/posts/aws-lambda-nmgvbaj4o) · Towards Dev · 0 upvotes · 0 comments - [Serverless Architecture: When to Use It \(and When Not To\)](https://daily.dev/posts/serverless-architecture-when-to-use-it-and-when-not-to--3trxabnfp) · Syncfusion · 0 upvotes · 0 comments - [Serverless is the ultimate place to experiment](https://daily.dev/posts/serverless-is-the-ultimate-place-to-experiment-kz51wsjw2) · Serverless · 0 upvotes · 0 comments --- Tags: [#aws](https://daily.dev/tags/aws), [#nodejs](https://daily.dev/tags/nodejs), [#serverless](https://daily.dev/tags/serverless), [#aws-lambda](https://daily.dev/tags/aws-lambda) [View this post on daily.dev](https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Announcing AWS Lambda Web Functions","url":"https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw"},"datePublished":"2026-10-13T00:13:26.661Z","dateModified":"2026-10-13T21:25:41.151Z","description":"AWS Lambda Web Functions is a new serverless form factor that runs standard HTTP web applications (Express, Hono, Fastify, Next.js, or any Node.js framework)...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8d1a76d789cb9961dfd6b5648ad98a8d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8d1a76d789cb9961dfd6b5648ad98a8d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"AWS","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AWS","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/aws","url":"https://daily.dev/sources/aws"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"aws,nodejs,serverless,aws-lambda","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AWS","item":"https://daily.dev/sources/aws"},{"@type":"ListItem","position":3,"name":"Announcing AWS Lambda Web Functions"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/announcing-aws-lambda-web-functions-vjdzg5fbw#faq","mainEntity":[{"@type":"Question","name":"What is AWS Lambda Web Functions and how is it different from regular Lambda functions?","acceptedAnswer":{"@type":"Answer","text":"AWS Lambda Web Functions is a new Lambda form factor that runs standard port-listening HTTP servers, like Express, Hono, Fastify, or Next.js, without rewriting code into an event handler. Unlike classic Lambda (now called Event Functions), which uses single-concurrent execution with wall-clock billing, Web Functions support up to 128 concurrent requests per execution environment and bill based on active CPU time rather than wall-clock time. Teams weighing serverless options for HTTP backends can track changes like this one on daily.dev."}},{"@type":"Question","name":"How do I deploy a Node.js Express app to AWS Lambda Web Functions?","acceptedAnswer":{"@type":"Answer","text":"Deploy an existing Express.js app unchanged with the command `aws lambda-web deploy --name my-web-app --code ./my-app`, which bundles the source, creates the Web Function, publishes a revision, attaches an endpoint, and returns a live HTTPS URL in under a minute. Locally, set the AWS_LAMBDA_HTTP_ENDPOINT environment variable to the host and port, for example 127.0.0.1:3000, to run the same code without Lambda-specific adapters. Developers shipping serverless Node.js apps can follow deployment changes like this through daily.dev."}},{"@type":"Question","name":"Which AWS regions and Node.js runtime does Lambda Web Functions support at launch?","acceptedAnswer":{"@type":"Answer","text":"At launch, Lambda Web Functions is available in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland), running Node.js 24 (nodejs24.x) on Arm64 architecture. It also supports Amazon VPC connectivity so functions can reach resources inside a VPC. Architects planning multi-region serverless rollouts can check platform availability details via daily.dev."}}]} ```