AWS lambda documentation change
Summary
Changed 'Firecracker microVM' to 'Firecracker MicroVM' for consistent capitalization.
Security assessment
Capitalization update only. The security context about snapshot encryption and execution environment initialization remains unmodified.
Diff
diff --git a/lambda/latest/dg/snapstart.md b/lambda/latest/dg/snapstart.md index 26718453d..f0d0f954a 100644 --- a//lambda/latest/dg/snapstart.md +++ b//lambda/latest/dg/snapstart.md @@ -13 +13 @@ Lambda SnapStart can provide as low as sub-second startup performance, typically -The largest contributor to startup latency (often referred to as cold start time) is the time that Lambda spends initializing the function, which includes loading the function's code, starting the runtime, and initializing the function code. With SnapStart, Lambda initializes your function when you publish a function version. Lambda takes a [Firecracker microVM](https://aws.amazon.com/blogs/opensource/firecracker-open-source-secure-fast-microvm-serverless/) snapshot of the memory and disk state of the initialized [execution environment](./lambda-runtime-environment.html), encrypts the snapshot, and intelligently caches it to optimize retrieval latency. +The largest contributor to startup latency (often referred to as cold start time) is the time that Lambda spends initializing the function, which includes loading the function's code, starting the runtime, and initializing the function code. With SnapStart, Lambda initializes your function when you publish a function version. Lambda takes a [Firecracker MicroVM](https://aws.amazon.com/blogs/opensource/firecracker-open-source-secure-fast-microvm-serverless/) snapshot of the memory and disk state of the initialized [execution environment](./lambda-runtime-environment.html), encrypts the snapshot, and intelligently caches it to optimize retrieval latency.