It should just accept a docker container (which normal lambdas can) or a WASM blob that exposes HTTP over a standard port.
Could use optional headers for extra integration points (eg. better per-request resource usage tracking for scaling).
Re:AWS Lambda Web Functions
by julianwood on Tuesday October 13, 2026 @05:46PM
(#50079328)
Thanks, Have a look at our Lambda roadmap for Web Functions which shows some of the things we're already working on: https://github.com/orgs/aws/projects/286/views/1?filterQuery...
Yep, I see container support is marked coming soon: https://github.com/aws/aws-lambda-roadmap/issues/103 This is your killer feature!
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.