Starting next August, Amazonâs AWS Lambda will begin charging for the initialization phase of its managed runtimes. This change, framed as a move towards billing standardization, has sparked debate in the community over its implications on pricing. Traditionally, only the INVOKE phase was billed, with the INIT phase exempted. Now, with this update, the INIT phase will contribute to costs, although AWS claims most users will see negligible increases, as cold starts only occur in about 1% of all invocations, based on their analysis of typical workloads.
Starting next August, AWS Lambda will begin charging for the INIT phase for managed runtimes, aiming for standardization despite perceptions of a potential price increase.
Most users will see minimal impact on their overall Lambda bill from this change. According to an analysis, INIT phases typically occur in under 1% of invocations.
The Lambda execution lifecycle consists of three phases: INIT (cold start), INVOKE (processing), and SHUTDOWN, with the INIT phase now included in the billing.
Only the INVOKE phase was previously billed for managed runtimes, but going forward the INIT phase will be billed similarly, influencing the overall billing structure.
Collection
[
|
...
]