AWS lambda documentation change
Summary
Changed 'Firecracker microVMs' to 'Firecracker MicroVMs' for consistent capitalization.
Security assessment
Change is purely cosmetic capitalization of 'MicroVMs' with no alteration to security-related content about isolation boundaries or container security limitations.
Diff
diff --git a/lambda/latest/dg/lambda-managed-instances-capacity-providers.md b/lambda/latest/dg/lambda-managed-instances-capacity-providers.md index aa5bc947e..3c3fb09ef 100644 --- a//lambda/latest/dg/lambda-managed-instances-capacity-providers.md +++ b//lambda/latest/dg/lambda-managed-instances-capacity-providers.md @@ -28 +28 @@ When you create a capacity provider, you specify: -Capacity providers serve as the security boundary for Lambda functions within your VPC, replacing Firecracker-based isolation. Functions execute in containers within instances, but containers do not provide strong security isolation between functions, unlike Firecracker microVMs. +Capacity providers serve as the security boundary for Lambda functions within your VPC, replacing Firecracker-based isolation. Functions execute in containers within instances, but containers do not provide strong security isolation between functions, unlike Firecracker MicroVMs.