AWS Builder Center
🚀 Your Web App. Now on Lambda. ☁️

🚀 Your Web App. Now on Lambda. ☁️

Deploy your Node.js app with less setup. AWS Lambda Web Functions brings concurrent requests, active CPU billing, and multi-region deployment to your familiar web frameworks. Here’s what’s new and why it matters. ⚡

Series: Free-AWS-Certifications (5 articles)

  1. …
  2. 5
    🚀 Your Web App. Now on Lambda. ☁️ This article
AWS Lambda Web Functions: a simpler way to deploy Node.js web apps
Getting an existing web application onto serverless infrastructure can involve extra work: adapting the server to an event handler, adding wrappers, and configuring how HTTP requests reach the application.
AWS Lambda Web Functions makes that process more straightforward.
Your application runs as a standard HTTP server, listening on a port. You can use familiar frameworks such as Express, Hono, Fastify, or Next.js, while Lambda manages the infrastructure and scaling.
Three features stand out:
• Concurrent requests within one environment
Each environment can handle up to 128 simultaneous requests. Incoming traffic can share available capacity in warm environments, which can reduce the need to start additional ones.
• CPU and memory billed separately
CPU billing reflects active processing. Waiting for a database or an external API consumes little CPU, while memory remains metered throughout the environment’s lifetime. That makes the model interesting for applications that spend much of their time waiting on other services.
• Deployment across multiple regions
You can deploy to several supported regions and expose one global URL. AWS configures routing toward the region with the lowest latency for each caller on a best-effort basis.
Consider a URL health checker. Most of its work involves sending requests and waiting for responses. Or think of an AI application that streams responses from a model provider. These are the kinds of workloads where the execution and billing model could be useful.
Web Functions also supports gradual releases through traffic splitting between revisions and integration with CloudFront for cached assets and dynamic requests.
At launch, it supports Node.js 24 on Arm64 in five AWS regions. Before migrating, check application compatibility, regional availability, authentication, and expected costs.
For developers building APIs, web applications, or streaming experiences, this gives Lambda a programming model that fits the HTTP servers they already use.
leave your thoughts below 👇🏻

Series: Free-AWS-Certifications (5 articles)

  1. …
  2. 5
    🚀 Your Web App. Now on Lambda. ☁️ This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article