AWS lambda documentation change
Summary
Updated two occurrences of 'Firecracker microVM' to 'Firecracker MicroVM' for consistent capitalization.
Security assessment
Changes are minor capitalization updates without modifying security implications of isolation models or tenancy descriptions. Security context about Firecracker vs container isolation remains unchanged.
Diff
diff --git a/lambda/latest/dg/lambda-managed-instances.md b/lambda/latest/dg/lambda-managed-instances.md index 992265935..bab1b7443 100644 --- a//lambda/latest/dg/lambda-managed-instances.md +++ b//lambda/latest/dg/lambda-managed-instances.md @@ -66 +66 @@ Lambda Managed Instances support multi-concurrent invocations, where one executi -Lambda (default) compute type is multi-tenant, making use of Firecracker microVM technology to provide isolation between execution environments running on shared Lambda fleets. Lambda Managed Instances run in your account, providing the latest EC2 hardware and pricing options. Managed Instances use containers running on EC2 Nitro instances to provide isolation rather than Firecracker. Capacity providers serve as the security boundary for Lambda functions. Functions execute in containers within instances. +Lambda (default) compute type is multi-tenant, making use of Firecracker MicroVM technology to provide isolation between execution environments running on shared Lambda fleets. Lambda Managed Instances run in your account, providing the latest EC2 hardware and pricing options. Managed Instances use containers running on EC2 Nitro instances to provide isolation rather than Firecracker. Capacity providers serve as the security boundary for Lambda functions. Functions execute in containers within instances. @@ -100 +100 @@ Concurrency model | Single concurrency model where one execution environment can -Tenancy and isolation | Multi-tenant, using Firecracker microVM technology to provide isolation between execution environments running on shared Lambda fleets | Run in your account, using EC2 Nitro to provide isolation. Capacity providers serve as the security boundary, with functions executing in containers within instances +Tenancy and isolation | Multi-tenant, using Firecracker MicroVM technology to provide isolation between execution environments running on shared Lambda fleets | Run in your account, using EC2 Nitro to provide isolation. Capacity providers serve as the security boundary, with functions executing in containers within instances