● Series · Part 1 of N · AWS Lambda
> AWS Lambda — How FaaS Works
Part 1 of an AWS Lambda series: what Function-as-a-Service is, the execution model behind it, and what's actually running underneath the abstraction.
Function Configuration
Memory 512 MB
Lambda allocates CPU proportional to memory. 1,769 MB ≈ 1 full vCPU. Memory ranges from 128 MB to 10,240 MB.
Simulated Execution Time 700 ms
Real Lambda functions can run up to 15 minutes. We use a short window here so you can see the lifecycle in action.
💡 What is AWS Lambda?
Invoke the Function
0 / 10 concurrentFirst invoke is a cold start (a fresh microVM boots). Subsequent invokes reuse the warm environment. Burst ×5 fires concurrent invocations to spawn new microVMs in parallel.
💡 How FaaS Works — The Execution Model
Execution Environments
live microVMs◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◯ —
Available
◌ Initializing
○ Idle (warm)
● Busy
◯ Available
💡 Cold Start vs Warm Start
Invocation Metrics
0 Invocations
0 Cold Starts
0 Warm Starts
0.0% Cold %
0 ms Billed
0.0000 GB·sec
$0.00 Est. Cost
0 Throttled