AWS Security ChangesHomeSearch

AWS lambda documentation change

Service: lambda · 2026-05-25 · Documentation low

File: lambda/latest/dg/lambda-runtime-environment.md

Summary

Updated terminology from 'Lambda SnapStart' to 'SnapStart' for consistency

Security assessment

Change only involves branding/naming standardization without security implications. Encryption reference remains unchanged.

Diff

diff --git a/lambda/latest/dg/lambda-runtime-environment.md b/lambda/latest/dg/lambda-runtime-environment.md
index e822daa34..cf8f2df36 100644
--- a//lambda/latest/dg/lambda-runtime-environment.md
+++ b//lambda/latest/dg/lambda-runtime-environment.md
@@ -108 +108 @@ The `Init` phase ends when the runtime and all extensions signal that they are r
-When [Lambda SnapStart](./snapstart.html) is activated, the `Init` phase happens when you publish a function version. Lambda saves a snapshot of the memory and disk state of the initialized execution environment, persists the encrypted snapshot, and caches it for low-latency access. If you have a before-checkpoint [runtime hook](./snapstart-runtime-hooks.html), then the code runs at the end of `Init` phase.
+When [SnapStart](./snapstart.html) is activated, the `Init` phase happens when you publish a function version. Lambda saves a snapshot of the memory and disk state of the initialized execution environment, persists the encrypted snapshot, and caches it for low-latency access. If you have a before-checkpoint [runtime hook](./snapstart-runtime-hooks.html), then the code runs at the end of `Init` phase.