AWS Security ChangesHomeSearch

AWS lambda: Lambda MicroVMs: supported CPU architectures and connection quota update

Service: lambda · 2026-11-06 · Documentation low

File: lambda/latest/dg/gettingstarted-limits.md

Summary

Changes the Lambda MicroVMs note heading to 'Supported CPU architectures', updates supported architectures to x86_64 and ARM64, and revises the concurrent connections per MicroVM quota to a floor of 150 plus 50 per additional vCPU up to 600.

Security assessment

The changed lines are quota/architecture limits for Lambda MicroVMs with no mention of authentication, encryption, or vulnerability remediation; the connection-limit change is a capacity constraint, not a security control.

Evidence

+Concurrent connections per MicroVM | Floor of 150, plus 50 per additional vCPU, up to a maximum of 600 | No  

Diff

diff --git a/lambda/latest/dg/gettingstarted-limits.md b/lambda/latest/dg/gettingstarted-limits.md
index 5e9af45..ce31b97 100644
--- a//lambda/latest/dg/gettingstarted-limits.md
+++ b//lambda/latest/dg/gettingstarted-limits.md
@@ -138 +138 @@ Lambda MicroVMs sets quotas for compute, storage, and API requests. Quotas marke
-###### Note
+###### Supported CPU architectures
@@ -140 +140 @@ Lambda MicroVMs sets quotas for compute, storage, and API requests. Quotas marke
-Lambda MicroVMs support the ARM64 (AWS Graviton) architecture.
+Lambda MicroVMs supports the `x86_64` and `ARM64` architectures.
@@ -161 +161 @@ Resource | Limit | Adjustable
-Concurrent connections per MicroVM | 8 (1 vCPU), 16 (2 vCPU), 32 (4 vCPU), 64 (8 vCPU), 128 (16 vCPU) | No  
+Concurrent connections per MicroVM | Floor of 150, plus 50 per additional vCPU, up to a maximum of 600 | No