Skip to content- Sources: primary, discussion
- Summary: Easel measured six Web Functions environments in us-east-1 staying alive for 313 to 411 seconds after their last request, with memory about 88% of compute and request cost at list prices. Exiting environments after 10 seconds idle cut metered time about 20 times, but AWS recorded each exit as a runtime failure, so Easel moved apps to its own hosts with Lambda for overflow.
- Why it matters: Low-traffic apps on Web Functions can pay for minutes of idle memory per request, which changes the cost math for many small deployments.
- Background: AWS announced Lambda Web Functions in October 2026 with native HTTP servers, concurrent requests per environment and active CPU billing. Memory is billed for an environment's whole lifetime, and AWS documents no idle timeout, which is the gap this post measures.