Lambda Web Functions Walkthrough

Same Node.js HTTP server you already write — on Lambda, without rewriting it as an event handler.

Get started Concepts

Tip

Web FunctionsWeb Functions
Lambda compute type that runs a standard Node.js HTTP server listening on a port, with a built-in HTTPS endpoint and multi-concurrency per environment. are for web apps and HTTP APIs — Express, Hono, SSR, webhooks, streaming responses. Built-in HTTPS, multi-concurrency, scale to zero, pay for active CPUactive CPU
Billable CPU time while the runtime and your code actively use the CPU — waiting on I/O is not billed as active CPU, but memory still accrues while the environment exists. not idle wait. No adapters. No fleet to manage.

This lab

Local listen → console create → prove → logs → optional CLI → teardown

Local listendemo/ on 127.0.0.1

Console createwf-hello / dev

Provecurl -i

Logsrequest id

Optional CLIExpress redeploy

Teardowndelete wf-hello

~30–45 min. Public Application-managed URL — tear down when done. Regions / IAM → Prerequisites.

Path

ToolingNode and curl

PrerequisitesAccount, Regions, IAM

ConceptsWeb vs Event vs MicroVMs

Start the walkthroughLocal listen → create → prove → teardown