What changes
AWS announced on November 17 that Event Functions on Lambda Managed Instances can scale to zero execution environments while idle and start again when invoked. Previously, a minimum number had to remain running.
The feature is available in commercial AWS Regions supporting Lambda Managed Instances. AWS points to development, test and intermittent processing workloads; this is not an announcement of universal free hosting.
A zero minimum is different from deactivation
The guide says to set MinExecutionEnvironments to 0 and MaxExecutionEnvironments above 0 for the relevant qualified function version. Both values must be supplied together, because an omitted value returns to its default.
Setting both values to 0 instead deactivates the version. That version does not start serving traffic again just because a request arrives.
Know the restart and billing limits
After a function has scaled to zero, AWS says an invocation receives HTTP 429 while an execution environment starts. Provisioning typically takes a few minutes and can take longer with lengthy initialization. The guide recommends retrying throttled synchronous requests with suitable backoff, or retaining minimum capacity for latency-sensitive work.
EC2 instance charges continue until termination finishes. An instance hosting other functions keeps running. Background CPU activity and deployments can also stop the last environment from scaling in, so a zero setting does not guarantee an immediately zero infrastructure bill.



