Contents

AWS has announced AWS Lambda Web Functions, which lets developers deploy Node.js web applications directly to Lambda. According to the supplied Publickey article dated October 20, 2026, it supports frameworks including Next.js, Express, Hono, and Fastify and is available in five regions, including Tokyo.

Key Points#

  • Web Functions lets you run Node.js web applications on Lambda without managing a separate HTTP adapter.
  • Each execution environment uses Node.js 24, has 2 GB of memory, and supports up to 128 concurrent requests.
  • The request timeout defaults to 30 seconds and can be configured from 3 seconds to 15 minutes.
  • Before using it in production, check AWS documentation for pricing, supported framework features, and deployment requirements.

What Changes for Web Applications#

Web Functions provides the web server capabilities that Node.js frameworks require. Instead of converting HTTP requests for a traditional Lambda function handler, you can deploy applications built around a Node.js web server.

The announcement lists support for Next.js, Express, Hono, and Fastify. According to the article, the existing event-driven function model will also be named “Lambda Event Functions.”

The practical benefit for teams with existing Node.js applications is simpler deployment. However, “direct deployment” does not guarantee that every framework feature, dependency, or hosting integration will work without configuration.

Understand the Runtime Limits#

The configuration described in the article reveals specific limits to evaluate before migrating an application.

| Setting | Reported Value | |---|---| | Runtime | Node.js 24 | | Memory per execution environment | 2 GB | | Default JavaScript heap | 1,024 MB | | Concurrent requests per environment | Up to 128 | | Default timeout | 30 seconds | | Configurable timeout | 3–900 seconds |

This concurrency figure refers to the number of requests processed simultaneously within a single execution environment. It does not indicate the application's overall capacity, throughput, or response time. These depend on workload characteristics, scaling, and service quotas, which the supplied article does not detail.

Memory requires attention because concurrent requests share the execution environment's resources. Applications that handle large payloads or perform server-side rendering need testing at realistic concurrency levels. Also, distinguish the 2 GB memory allocation from the default JavaScript heap limit.

Check Region Availability#

The article lists the following five supported AWS regions.

  • Asia Pacific: Tokyo.
  • US East: Northern Virginia, Ohio.
  • US West: Oregon.
  • Europe: Ireland.

Availability in Tokyo makes this an immediate option for teams serving users in Japan. However, choosing Tokyo alone does not guarantee acceptable latency. Database location, external API calls, and application processing also affect response times.

Before planning a migration, check whether Web Functions supports the regions you need. For applications with regional disaster recovery requirements, also confirm that a suitable secondary region is available.

Test Before Migrating Production#

Start with a small application or a route that can be tested in isolation. Check the deployment steps in AWS documentation and validate these four areas.

1. Runtime compatibility: Check that dependencies, including native modules and build artifacts, support Node.js 24. 2. Framework behavior: Test the features your application actually uses, such as server-side rendering, middleware, streaming, and static assets. 3. Behavior under load: Measure latency, errors, and memory usage as you increase concurrent requests. 4. Operational requirements: Check logging, secrets, authentication, deployment rollbacks, and connections to databases and private services.

A successful deployment confirms that the application starts. It does not prove that the execution model suits your production workload.

The supplied article does not clarify pricing, cold-start behavior, scaling quotas, or detailed framework compatibility. These need checking, especially when comparing Web Functions with existing hosting services. Support for Next.js alone is insufficient to establish that the associated deployment workflows and managed features are equivalent.

Next Steps#

Deploy one representative route in a supported region, record response latency, error rates, and memory usage during load testing, then decide whether to migrate the rest of the application.

Source: https://www.publickey1.jp/blog/26/aws_lambdanextjshononodejsaws_lambda_web_functions.html

Contents