{
 "features_resolved": {
  "snapshot_any": true,
  "snapshot_mem": true,
  "fork": false,
  "pause_resume": true,
  "persistent_disk": true,
  "whole_disk": true,
  "persist_scope": true,
  "volumes": false,
  "auto_stop_idle": true,
  "long_sessions": false,
  "custom_image": true,
  "image_snapshot": true,
  "image_oci": true,
  "vm_isolation": true,
  "docker_inside": false,
  "nested_virt": false,
  "root": true,
  "systemd": false,
  "browser": false,
  "desktop": false,
  "computer_use": false,
  "code_interpreter": false,
  "browser_control": null,
  "desktop_control": null,
  "browser_and_desktop": false,
  "anti_bot": false,
  "captcha_solving": false,
  "residential_ip": false,
  "agent_harnesses": false,
  "ssh": false,
  "public_ipv4": false,
  "inbound_https": true,
  "custom_domain": false,
  "raw_tcp_inbound": false,
  "egress_allowlist": true,
  "open_internet": true,
  "static_egress_ip": true,
  "private_network": true,
  "self_host": false,
  "byoc": false,
  "open_source": false,
  "soc2": true,
  "hipaa": true,
  "sso": true,
  "gpu": false,
  "arm64": true,
  "windows": false,
  "macos": false,
  "lang_python": false,
  "lang_node": false,
  "lang_go": null,
  "lang_rust": null,
  "lang_java": null,
  "gpu_desktop": false,
  "credential_injection": null,
  "egress_http_rules": true,
  "wake_on_request": true,
  "live_resize": false,
  "fork_running": false,
  "memory_snapshot_fork": false,
  "webhooks": null,
  "scheduled_wakeups": null,
  "audit_logs": null,
  "eu_data_residency": true,
  "zero_data_retention": null,
  "scoped_api_keys": null,
  "spend_limits": null,
  "mcp_server": false,
  "usage_api": true,
  "snapshot_auto": true,
  "snapshot_on_demand": true,
  "harness_api": false,
  "own_agent_api": false,
  "fast_boot": null,
  "strong_isolation": true,
  "ingress_rules": true,
  "guest_firewall": true,
  "secret_proxy": false,
  "secret_proxy_any": false,
  "volume_attach": false,
  "volume_shared": false,
  "sidecar": null,
  "fuse": true,
  "kernel_features": true,
  "burst": null
 },
 "company": {
  "id": "aws-lambda-microvms",
  "checked": "2026-09-30",
  "company": "Amazon.com, Inc. (AWS Lambda MicroVMs, part of Amazon Web Services)",
  "ownership": {
   "value": "subsidiary",
   "parent": "Amazon.com, Inc. (Amazon Web Services)",
   "source": "https://aws.amazon.com/lambda/pricing/",
   "quote": "Lambda MicroVMs is an AWS Lambda serverless compute environment offering."
  },
  "stage": {
   "value": "public",
   "source": "https://ir.aboutamazon.com/news-release/news-release-details/2025/Amazon-com-Announces-Fourth-Quarter-Results/default.aspx",
   "quote": "Amazon.com, Inc. is a publicly traded company (NASDAQ: AMZN); AWS is a reporting segment within Amazon's public filings.",
   "confidence": "high",
   "note": "AWS Lambda MicroVMs is a feature/product line of AWS, not an independently funded entity; Amazon is a public company, so no separate funding rounds apply."
  },
  "accelerators": [],
  "total_funding_usd": {
   "value": null,
   "status": "unknown"
  },
  "last_round": {
   "type": null,
   "amount_usd": null,
   "date": null,
   "leads": [],
   "status": "unknown",
   "source": "",
   "quote": ""
  },
  "investors": [],
  "portfolio_listings": [],
  "revenue": {
   "value_usd": 107560000000,
   "kind": "annual revenue",
   "as_of": "2024",
   "status": "confirmed",
   "basis": "AWS segment full-year 2024 net sales as reported in Amazon's Q4 2024 earnings release (Amazon.com, Inc. consolidated financials); figure is for the whole AWS segment, not the Lambda MicroVMs product specifically, whose standalone revenue is not broken out.",
   "source": "https://ir.aboutamazon.com/news-release/news-release-details/2025/Amazon-com-Announces-Fourth-Quarter-Results/default.aspx",
   "quote": "AWS segment sales increased 19% year-over-year to $107.6 billion in 2024."
  },
  "employees": {
   "value": null,
   "source": ""
  },
  "note": "Not an independent company: AWS Lambda MicroVMs is a feature of AWS Lambda, itself a service of Amazon Web Services, a segment of the publicly traded Amazon.com, Inc. (NASDAQ: AMZN). No separate ownership, accelerator, funding, or stage data applies; revenue shown is Amazon's whole AWS segment for FY2024, not a figure specific to Lambda MicroVMs, which was announced in 2025/2026 and has no standalone financials disclosed."
 },
 "id": "aws-lambda-microvms",
 "name": "AWS Lambda MicroVMs",
 "url": "https://aws.amazon.com/lambda/pricing/",
 "category": "hyperscaler",
 "isolation": "firecracker",
 "modes": [
  {
   "key": "on-demand-arm64",
   "label": "Arm64 (Graviton) baseline, us-east-1/us-east-2/us-west-2/ap-south-1",
   "flags": [],
   "os": [
    "linux"
   ],
   "regions": [
    "us",
    "asia"
   ],
   "gpu_only": false,
   "features": {
    "arm64": true,
    "isolation": "firecracker"
   },
   "pricing": "resource",
   "vcpu_h": 0.0997,
   "ram_gib_h": 0.0132,
   "cpu_basis": "alloc",
   "ram_basis": "alloc",
   "active_floor": 0,
   "ram_per_vcpu": [
    2,
    2
   ],
   "ram_fixed_per_vcpu": 2,
   "vcpu_options": [
    0.25,
    0.5,
    1,
    2,
    4
   ],
   "min_vcpu": 0.25,
   "max_vcpu": 4,
   "max_ram_gib": 8,
   "sizes": null,
   "pool_tiers": null,
   "requires_always_on": false,
   "always_on_month_per_instance": null,
   "commit_note": null,
   "min_billed_seconds": 0,
   "granularity_s": 1,
   "start_fee": 0,
   "boot_overhead_s": null,
   "multiplier": 1,
   "windows_vcpu_h": null,
   "gpu": null,
   "note": "Price List API Lambda-MicroVM-vCPU-Second-ARM $0.0000276944 = $0.0997/vCPU-h, Memory-GB-Second-ARM $0.0000036667 = $0.0132/GB-h. Baseline billed per second while running (2 GB : 1 vCPU; default 1 vCPU/2 GB, max baseline 4 vCPU/8 GB); automatic vertical burst up to 4x baseline (16 vCPU/32 GB) billed only while consumed. ap-south-1 matches us rates. Basis verified 2026-09-28: \"You pay for baseline compute resources while your MicroVM is running. When your workload consumes resources above the baseline, you are charged only for the active duration of the additional memory and vCPU consumed.\" (https://aws.amazon.com/lambda/pricing/). Baseline = alloc; burst via burst_share knob. Idle: \"After 5 minutes of inactivity, the MicroVM is automatically suspended based on the configured idle policy.\" (AWS launch blog).",
   "cpu_class": "shared"
  },
  {
   "key": "on-demand-arm64-eu",
   "label": "Arm64 baseline, eu-north-1 (cheapest EU)",
   "flags": [],
   "os": [
    "linux"
   ],
   "regions": [
    "eu"
   ],
   "gpu_only": false,
   "features": {
    "arm64": true,
    "isolation": "firecracker"
   },
   "pricing": "resource",
   "vcpu_h": 0.09975,
   "ram_gib_h": 0.013208,
   "cpu_basis": "alloc",
   "ram_basis": "alloc",
   "active_floor": 0,
   "ram_per_vcpu": [
    2,
    2
   ],
   "ram_fixed_per_vcpu": 2,
   "vcpu_options": null,
   "min_vcpu": 1,
   "max_vcpu": 4,
   "max_ram_gib": 8,
   "sizes": null,
   "pool_tiers": null,
   "requires_always_on": false,
   "always_on_month_per_instance": null,
   "commit_note": null,
   "min_billed_seconds": 0,
   "granularity_s": 1,
   "start_fee": 0,
   "boot_overhead_s": null,
   "multiplier": 1,
   "windows_vcpu_h": null,
   "gpu": null,
   "note": "EUN1 $0.000027709/vCPU-s, $0.000003669/GB-s. eu-west-1 is $0.10497/$0.013897 (the \"$0.0000291572\" figure a secondary source quoted is eu-west-1, not x86). Basis verified 2026-09-28: \"You pay for baseline compute resources while your MicroVM is running. When your workload consumes resources above the baseline, you are charged only for the active duration of the additional memory and vCPU consumed.\" (https://aws.amazon.com/lambda/pricing/). Baseline = alloc; burst via burst_share knob. Idle: \"After 5 minutes of inactivity, the MicroVM is automatically suspended based on the configured idle policy.\" (AWS launch blog).",
   "cpu_class": "shared"
  }
 ],
 "storage": {
  "included_disk_gib": 8,
  "disk_gib_month": 0,
  "disk_billed_when_stopped": false,
  "snapshot_gib_month": 0.0811,
  "paused_ram_billed": false
 },
 "network": {
  "egress_free_gib": 100,
  "egress_gib": 0.09,
  "ipv4_month": null,
  "ipv4_available": false,
  "internet": {
   "default": "configurable",
   "evidence": [
    {
     "quote": "By default, Lambda MicroVMs support outbound connectivity to the public internet without additional configuration.",
     "url": "https://aws.amazon.com/blogs/compute/announcing-lambda-microvms-serverless-compute-environments-with-vm-level-isolation-and-near-instant-startup/"
    },
    {
     "quote": "Each MicroVM exposes a dedicated HTTPS endpoint for inbound connectivity to individual ports.",
     "url": "https://aws.amazon.com/blogs/compute/announcing-lambda-microvms-serverless-compute-environments-with-vm-level-isolation-and-near-instant-startup/"
    }
   ]
  }
 },
 "plans": [
  {
   "name": "Pay-as-you-go",
   "fee": 0,
   "flags": [],
   "fee_is_credit": false,
   "included_usd": 0,
   "per_seat": 0,
   "concurrency": null,
   "max_session_h": 8,
   "max_vcpu": 16,
   "max_ram_gib": 32,
   "sizes_allowed": null,
   "note": "Hard maximum lifetime 8 h (28,800 s) counting running AND suspended time, not adjustable; after that the MicroVM is terminated. Idle auto-suspend is set per MicroVM via idlePolicy.maxIdleDurationSeconds (max 28,800 s); the 5-minute value is only the launch-blog example, not a default. Dedicated HTTPS endpoint per MicroVM."
  }
 ],
 "free": {
  "monthly_credit": 0,
  "one_time_credit": 200
 },
 "features": {
  "linux": true,
  "windows": false,
  "macos": false,
  "arm64": true,
  "gpu": false,
  "gpu_types": [],
  "snapshot": "mem",
  "pause_resume": true,
  "fork": false,
  "persistent_disk": true,
  "volumes": false,
  "auto_stop_idle": true,
  "max_session_h": 8,
  "custom_image": true,
  "docker_inside": false,
  "nested_virt": false,
  "root": true,
  "systemd": false,
  "browser": false,
  "desktop": false,
  "computer_use": false,
  "code_interpreter": false,
  "agent_harnesses": false,
  "ssh": false,
  "public_ipv4": false,
  "inbound_https": true,
  "custom_domain": false,
  "raw_tcp_inbound": false,
  "egress_allowlist": true,
  "static_egress_ip": true,
  "private_network": true,
  "self_host": false,
  "byoc": false,
  "open_source": false,
  "regions": [
   "us",
   "eu",
   "asia",
   "other"
  ],
  "soc2": true,
  "hipaa": true,
  "sso": true,
  "lang_python": false,
  "lang_node": false,
  "lang_go": null,
  "lang_rust": null,
  "lang_java": null,
  "gpu_desktop": false,
  "credential_injection": null,
  "egress_http_rules": true,
  "wake_on_request": true,
  "live_resize": false,
  "fork_running": false,
  "memory_snapshot_fork": false,
  "webhooks": null,
  "scheduled_wakeups": null,
  "audit_logs": null,
  "eu_data_residency": true,
  "zero_data_retention": null,
  "scoped_api_keys": null,
  "spend_limits": null,
  "mcp_server": false,
  "isolation": "firecracker",
  "image_oci": true,
  "snapshot_auto": true,
  "snapshot_on_demand": true,
  "harness_api": false,
  "egress_allowlist_level": "ip",
  "ingress_rules": true,
  "guest_firewall": true,
  "secret_proxy": false,
  "volume_attach": false,
  "volume_shared": false,
  "anti_bot": false,
  "captcha_solving": false,
  "egress_ip_type": "datacenter",
  "own_agent_api": false,
  "open_internet": true,
  "usage_api": true,
  "persist_scope": "whole"
 },
 "perf": {
  "cpu_runs_s": null,
  "cold_start_ms": null,
  "burst_tti_ms": null,
  "dax_s": null
 },
 "knobs": [
  {
   "id": "burst_share",
   "label": "Average burst above baseline (fraction of baseline)",
   "kind": "slider",
   "min": 0,
   "max": 3,
   "step": 0.1,
   "default": 0,
   "unit": "x",
   "options": null,
   "effect": "rate_factor",
   "modes": null,
   "why": "Baseline-plus-consumption: resources used above the configured baseline (up to 4x) are billed per second on top; 0.5 = on average 50% extra above baseline. Engine rate multiplier = 1 + value.",
   "map": {
    "offset": 1,
    "scale": 1
   }
  }
 ],
 "caveats": [
  "All rates from the AWS Price List API (AWSLambda, publication 2026-09-19). Regions with MicroVM SKUs: us-east-1, us-east-2, us-west-2, eu-west-1, eu-north-1, eu-central-1, ap-south-1, ap-northeast-1, ap-southeast-1, ap-southeast-2.",
  "The knob rate_factor for burst is an approximation: burst is billed only for seconds it is consumed, at the same unit rates (per pricing page \"baseline-plus-consumption\").",
  "Snapshots (suspend = memory+disk): storage $0.0001111111/GB-h = $0.0811/GB-month; write $0.0037977/GB; read (on start/resume) $0.0015468/GB; MicroVM image storage has a 1-week minimum retention. Suspended VMs pay no compute.",
  "Disk: max disk space scales with the baseline (microvms-images.html sizing table): 8 GB for the 0.5 GB / 0.25 vCPU, 1 GB / 0.5 vCPU and 2 GB / 1 vCPU (default) baselines, 16 GB at 4 GB / 2 vCPU, 32 GB at 8 GB / 4 vCPU (\"| 8 GB memory, 4 vCPU | 32 GB memory, 16 vCPU | 32 GB |\", checked 2026-10-14). included_disk_gib = 8 is the default-baseline figure; the engine has no per-shape disk cap for resource modes, so a request above the shape's max disk is not flagged. Running disk: the AWS Price List API (AWSLambda us-east-1, fetched 2026-09-28) has only vCPU, memory and snapshot storage/read/write SKUs for MicroVMs, no running-disk meter, so disk_gib_month = 0 (disk of a running MicroVM is not billed separately; it is billed as snapshot storage once suspended). Minimum billed duration and any per-launch fee are not published. Whether Compute Savings Plans or the Lambda free tier apply is not stated (assumed no).",
  "Max lifetime: 8 h hard cap, not adjustable. Quotas page: \"Maximum execution duration per MicroVM | 8 hours (28,800 seconds) | No\" (adjustable: No); launching page: --maximum-duration-in-seconds is \"The maximum total lifespan of the MicroVM, including both running and suspended time. Lambda terminates the MicroVM when this duration is exceeded. Range: 1–28,800 seconds (8 hours).\" (checked 2026-10-14).",
  "Identical to the announced AgentCore Runtime v2 committed baseline rates ($0.0997/vCPU-h, $0.0132/GB-h).",
  "Internet egress (AWS Price List API, AWSDataTransfer us-east-1, 2026-09): first 100 GB/month free aggregated across all services and regions, then $0.09/GB first 10 TB, $0.085 next 40 TB, $0.07 next 100 TB, $0.05 over 150 TB. eu-west-1 is also $0.09; ap-south-1 $0.1093; ap-northeast-1 $0.114; ap-southeast-1 $0.12 (first-10-TB tier). The engine uses the flat us-east-1 first tier.",
  "VPC access via Lambda Network Connector; NAT gateway gotcha: tasks/functions in private subnets reach the internet through a NAT gateway at $0.045/h per gateway (~$32.85/month per AZ) plus $0.045/GB processed (us-east-1; eu-north-1 $0.046, ap-south-1 $0.056), charged ON TOP of the $0.09/GB egress. Not modelled; public IPv4 ($0.005/h) is the usual alternative.",
  "Snapshot storage is region-priced: us-east-1/us-east-2/us-west-2 $0.0001111/GB-h ($0.0811/GB-mo), eu-north-1 $0.0001161 ($0.0848), ap-south-1 $0.0001267 ($0.0925), eu-west-1/eu-central-1 $0.0001322 ($0.0965), ap-northeast-1/ap-southeast-1/ap-southeast-2 $0.0001333 ($0.0973). The EU mode inherits the us-east-1 figure.",
  "Suspended state is kept for at most 8 hours ('you can suspend a running MicroVM for up to 8 hours'); suspendedDurationSeconds sets auto-termination. Per-MicroVM limits: concurrent connections 8 (1 vCPU) to 128 (16 vCPU); requests/s 40 (4 vCPU / 8 GB) to 160 (16 vCPU / 32 GB). SLA 99.5% (Lambda SLA). Shell access (not SSH) via SHELL_INGRESS connector and a shell auth token."
 ],
 "sources": [
  "https://aws.amazon.com/lambda/pricing/",
  "https://aws.amazon.com/blogs/compute/announcing-lambda-microvms-serverless-compute-environments-with-vm-level-isolation-and-near-instant-startup/",
  "https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSLambda/current/region_index.json",
  "https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html",
  "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
  "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html"
 ],
 "fleet": {
  "default_max_instances": null,
  "default_max_vcpu": null,
  "default_max_gpus": null,
  "raise": "automatic",
  "raise_time_days": null,
  "verification": "Personal details, email and phone; payment card may be required.",
  "tiers": null,
  "notes": "New-account memory quota is explicitly reduced and unspecified, raised automatically with usage. Published memory pool is 400 GB per region or 1,024 GB in us-east-1/us-west-2/us-east-2/ap-northeast-1, burstable to 4x, adjustable via Service Quotas; it counts MicroVMs in RUNNING or SUSPENDED state. Machine count depends on configured RAM, not Lambda invocation concurrency. API rate limits per account per region (adjustable): RunMicrovm 5 TPS (burst 5), ResumeMicrovm 5 TPS, SuspendMicrovm 2 TPS, TerminateMicrovm 10 TPS, CreateMicrovmShellAuthToken 5 TPS. Concurrent image builds 5 (10 in 4 regions).",
  "sources": [
   "https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html",
   "https://aws.amazon.com/free/complete-signup/"
  ],
  "researched": "2026-09-28"
 },
 "audit_2026_09_29": {
  "applied": 6,
  "source": "checked against the provider's live pricing and docs pages",
  "reviewed": 4
 },
 "feature_evidence": {
  "snapshot_auto": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "Idle policy (automatic) – Configure maxIdleDurationSeconds in the idle policy. If no traffic arrives at the MicroVM endpoint for that duration, Lambda suspends the MicroVM automatically.",
   "note": "Trigger: no traffic on the endpoint for maxIdleDurationSeconds (blog example 300 s; max 28,800 s). Suspend checkpoints memory AND disk ('SUSPENDED ... /suspend hook completed, memory and disk state checkpointed', microvms-how-it-works.html); with autoResumeEnabled=true the next inbound request resumes it with processes intact. Suspended state is kept only for suspendedDurationSeconds and total lifetime incl. suspended time is capped at 28,800 s (8 h), then the MicroVM is terminated and state is lost. Hitting maximumDurationInSeconds terminates (no snapshot).",
   "checked": "2026-09-29"
  },
  "snapshot_on_demand": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "API call (explicit) – Call suspend-microvm to suspend immediately",
   "note": "Only as suspend/resume of the same MicroVM: memory + disk are checkpointed and restored on resume-microvm. No named snapshots, no fork: the API (botocore lambda-microvms ops) has no snapshot/clone operation and new MicroVMs can only boot from MicroVM images, which are memory+disk Firecracker snapshots taken at image BUILD time from a Dockerfile, not from a running MicroVM. Suspended checkpoint lives at most within the 8 h lifetime.",
   "checked": "2026-09-29"
  },
  "harness_api": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "Anthropic hosts the agent loop and Claude model, while the Lambda MicroVM is where your tool calls run.",
   "note": "No AWS-side API to prompt/stream an agent; the lambda-microvms API has only image, run/suspend/resume/terminate and auth-token operations. AWS documents reference samples that make MicroVMs the self-hosted sandbox for Claude Managed Agents, Cursor Cloud Agents (self-hosted machines) and the OpenAI Agents API; the harness API there is the third party's, not AWS's. Also an 'AWS Lambda MicroVMs skill' for coding agents to build on the service (dev tooling, not a harness API).",
   "checked": "2026-09-29"
  },
  "egress_allowlist": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-networking.html",
   "quote": "When using VPC egress, outbound traffic is subject to security group rules and network ACLs governing traffic in your VPC.",
   "note": "Default egress connector INTERNET_EGRESS = open internet. To restrict, attach a customer-managed VPC egress Lambda Network Connector (subnets + security groups); SG egress rules / NACLs apply outside the VM. Domain-level filtering would need a separate AWS product in that VPC (e.g. Network Firewall / DNS Firewall), not part of MicroVMs. Connectors cannot be changed while a MicroVM is running. VPC egress to the internet needs NAT (extra cost).",
   "checked": "2026-09-29",
   "level": "ip"
  },
  "ingress_rules": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "All requests to a MicroVM endpoint require a JWE authentication token. There is no unauthenticated access option.",
   "note": "Tokens are scoped to one MicroVM, a port / port range / all ports, and an expiry (create-microvm-auth-token). NO_INGRESS connector disables inbound; SHELL_INGRESS connector + separate shell token for shell access. Private connectivity via PrivateLink interface endpoint (com.amazonaws.region.lambda-microvm) with endpoint policy (aws:ResourceAccount, aws:SourceVpc, aws:VpcSourceIp conditions). HTTPS only (HTTP/1.1, HTTP/2, WebSockets, gRPC, SSE); no raw TCP.",
   "checked": "2026-09-29"
  },
  "guest_firewall": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "Elevated capabilities enable operations such as mounting filesystems, creating network namespaces, or running eBPF programs. Capabilities are applied within the VM isolation boundary and do not affect the host or other MicroVMs.",
   "note": "Firecracker microVM with its own kernel. By default only 'a standard set of Linux capabilities'; iptables/nftables presumably needs additionalOsCapabilities [\"ALL\"] set on the image (derived, not explicitly documented).",
   "checked": "2026-09-29",
   "derived": true
  },
  "secret_proxy": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "The launcher only passes an AWS Secrets Manager reference to your Anthropic environment key; the MicroVM's execution role allows the code to read it at runtime.",
   "note": "Secrets are read inside the VM (Secrets Manager / SSM via execution role over IMDSv2, env vars at image level, or runHookPayload). No credential-injecting egress proxy documented.",
   "checked": "2026-09-29"
  },
  "volume_attach": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "The only required parameter is --image-identifier (which must be the ARN of the MicroVM image). All other parameters are optional.",
   "note": "The full RunMicrovm parameter set (image, version, execution role, idle policy, max duration, run-hook payload, logging, ingress/egress connectors; confirmed in botocore service-2.json) has no volume/storage parameter; only the root disk from the image snapshot. Self-mounting (e.g. NFS/EFS through a VPC connector with ALL capabilities) is conceivable but undocumented.",
   "checked": "2026-09-29"
  },
  "volume_shared": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "Sessions never share state.",
   "note": "No first-party shared volume or bucket mount; data sharing via S3 SDK calls. Same caveat as volume_attach (self-mounted NFS/EFS undocumented).",
   "checked": "2026-09-29"
  },
  "anti_bot": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "If you're building an application where multiple users or AI agents connect to a compute environment and run code (for example, interactive development environments, CI/CD systems, or sandboxes for AI) – you need compute environments that start fast, stay isolated between tenants, and don't require you to manage servers or networking.",
   "note": "not offered: outside the product's scope",
   "checked": "2026-09-30"
  },
  "captcha_solving": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "If you're building an application where multiple users or AI agents connect to a compute environment and run code (for example, interactive development environments, CI/CD systems, or sandboxes for AI) – you need compute environments that start fast, stay isolated between tenants, and don't require you to manage servers or networking.",
   "note": "not offered: outside the product's scope",
   "checked": "2026-09-30"
  },
  "egress_ip_type": {
   "value": "datacenter",
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-networking.html",
   "quote": "By default, Lambda MicroVMs have public internet access on the egress path.",
   "note": "Default egress (INTERNET_EGRESS connector) is a Lambda-managed AWS datacenter IP, not residential/mobile; a VPC egress connector routes through a customer NAT gateway/EIP, also AWS-owned datacenter address space. Same classification used for other AWS compute cards (aws-agentcore).",
   "checked": "2026-09-30"
  },
  "live_resize": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "You set the baseline by using the memory parameter when creating your MicroVM image. ... During peak activity, your MicroVM can automatically scale vertically up to 4x the baseline.",
   "note": "The baseline (vCPU/RAM floor) is fixed when the MicroVM image is created, not adjustable on a running MicroVM without a new image/run. The up-to-4x burst is automatic, best-effort headroom, not a user-triggered live resize of a running machine's allocation.",
   "checked": "2026-09-30"
  },
  "own_agent_api": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "Anthropic hosts the agent loop and Claude model, while the Lambda MicroVM is where your tool calls run.",
   "note": "not offered: outside the product's scope — MicroVMs is the sandbox/compute layer; the agent loop (browser/computer-use/research agent) is provided by third parties (Anthropic, OpenAI, Cursor) that use MicroVMs as a self-hosted execution backend, not an AWS-owned task agent.",
   "checked": "2026-09-30"
  },
  "lang_python": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "Lambda builds your application container image by running your Dockerfile on top of an operating system environment that is provided by a Lambda-managed MicroVM base image.",
   "note": "MicroVM base image is bare Amazon Linux 2023; there is no managed Python runtime layer as with classic Lambda functions — you must install Python yourself via your Dockerfile, same as aws-fargate/aws-ec2 in this dataset.",
   "checked": "2026-09-30"
  },
  "lang_node": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "Lambda builds your application container image by running your Dockerfile on top of an operating system environment that is provided by a Lambda-managed MicroVM base image.",
   "note": "Same as lang_python: bare Amazon Linux 2023 base image, Node.js must be installed via your own Dockerfile; no managed Node runtime is provided out of the box.",
   "checked": "2026-09-30"
  },
  "egress_http_rules": {
   "value": true,
   "source": "https://docs.aws.amazon.com/network-firewall/latest/developerguide/tls-inspection-configurations.html",
   "quote": "After decryption, Network Firewall inspects the traffic according to your firewall policy's stateful rules, and then re-encrypts it before sending it to its destination.",
   "note": "Only reachable via a customer-managed VPC egress Lambda Network Connector routed through AWS Network Firewall (separate paid service) with Suricata-compatible HTTP-header/host/URI rules; requires TLS inspection for HTTPS. Not a native per-MicroVM setting — same mechanism/consistency used for aws-fargate and aws-ec2 in this dataset.",
   "checked": "2026-09-30"
  },
  "static_egress_ip": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-networking.html",
   "quote": "To connect MicroVMs with resources in your private VPCs ... create a Lambda Network Connector with your VPC configuration.",
   "note": "Default INTERNET_EGRESS path has no fixed IP, but attaching a VPC egress connector lets outbound traffic go through a customer NAT Gateway with an Elastic IP, giving a fixed outbound address — the same NAT-gateway pattern noted in the card's own caveats and used for aws-fargate/aws-ec2 in this dataset.",
   "checked": "2026-09-30"
  },
  "hipaa": {
   "value": true,
   "source": "https://aws.amazon.com/compliance/hipaa-eligible-services-reference/",
   "quote": "AWS Lambda",
   "note": "\"AWS Lambda\" is listed on AWS's HIPAA-eligible services reference (BAA-covered). Lambda MicroVMs is part of the Lambda service/API surface; no MicroVMs-specific carve-out or exclusion was found, but this newer sub-feature isn't separately named on the list.",
   "checked": "2026-09-30"
  },
  "eu_data_residency": {
   "value": true,
   "source": "https://aws.amazon.com/lambda/pricing/",
   "quote": "eu-west-1, eu-north-1, eu-central-1",
   "note": "MicroVM SKUs exist in eu-west-1, eu-north-1, and eu-central-1 per the AWS Price List API; a customer can pin a MicroVM (and its snapshot/image storage) to an EU region.",
   "checked": "2026-09-30"
  },
  "persistent_disk": {
   "value": true,
   "corrected_from": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html",
   "quote": "SUSPENDING SUSPENDED /suspend hook completed, memory and disk state checkpointed. SUSPENDED RUNNING Traffic arrives (autoResumeEnabled=true) or explicit resume-microvm API call.",
   "note": "Suspend (pause) checkpoints disk+memory and resume restores it with files intact — files survive a stop/pause. Default behaviour: idle policy auto-suspends (default off unless configured) and the checkpoint is kept only up to the account's suspend duration; hitting maximumDurationInSeconds (max 8h total incl. suspended time) instead TERMINATEs the MicroVM and the disk state is lost (no snapshot taken on hard termination). So persistent_disk should be true, with the caveat that it's bounded to the 8h suspend/lifetime window, not indefinite.",
   "checked": "2026-09-30"
  },
  "fork": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "The only required parameter is --image-identifier (which must be the ARN of the MicroVM image). All other parameters are optional.",
   "note": "run-microvm only ever boots from a MicroVM image (a Firecracker snapshot built from a Dockerfile at image-build time); there is no parameter or API operation to start a new MicroVM from another running/suspended MicroVM's state, so machines cannot be cloned/forked.",
   "checked": "2026-09-30"
  },
  "fork_running": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "The only required parameter is --image-identifier (which must be the ARN of the MicroVM image). All other parameters are optional.",
   "note": "Same as fork: no operation clones a running MicroVM; new MicroVMs only start from a pre-built image snapshot, never from a live sibling.",
   "checked": "2026-09-30"
  },
  "memory_snapshot_fork": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html",
   "quote": "MicroVM image A MicroVM image is a resource that defines the application environment of a MicroVM. When you create an image, Lambda builds it into a snapshot that enables near-instant launch",
   "note": "Memory+disk snapshots exist only as (a) the build-time image snapshot and (b) the suspend/resume checkpoint of the SAME MicroVM — neither is exposed as a 'clone this MicroVM into N new running copies with memory' operation.",
   "checked": "2026-09-30"
  },
  "docker_inside": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "Lambda MicroVMs runs your application as a container within the MicroVM operating system environment. You define that container with your Dockerfile, and the FROM instruction in your Dockerfile sets the container base image for your application.",
   "note": "Docker/a Dockerfile is only used to BUILD the single application container that becomes the MicroVM's memory+disk snapshot at image-build time; the docs describe exactly one container per MicroVM running under the Amazon Linux 2023 guest kernel, with elevated OS capabilities (additionalOsCapabilities: [\"ALL\"]) documented only for mounting filesystems, network namespaces, and eBPF — never for a runtime docker/containerd daemon or 'docker run' inside the guest. No page confirms or denies a docker binary is present at runtime, so this is treated as not offered as documented, medium confidence rather than a clean explicit denial.",
   "checked": "2026-09-30"
  },
  "nested_virt": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-images.html",
   "quote": "By default, Lambda MicroVMs run with a standard set of Linux capabilities. You can grant elevated Linux capabilities using the additionalOsCapabilities field when creating or updating a MicroVM image. The only supported value is [\"ALL\"]. Elevated capabilities enable operations such as mounting filesystems, creating network namespaces, or running eBPF programs.",
   "note": "The documented list of what elevated capabilities unlock (mount, netns, eBPF) never mentions /dev/kvm or nested virtualization, and Firecracker microVMs do not expose hardware virtualization extensions to the guest by design — confirms no nested_virt.",
   "checked": "2026-09-30"
  },
  "ssh": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-networking.html",
   "quote": "The following protocols are supported on the inbound endpoint: HTTP/1.1, HTTP/2, WebSockets, gRPC, Server-Sent Events (SSE)",
   "note": "Inbound connectivity is exhaustively documented as HTTPS-endpoint protocols only (no raw TCP, no SSH/port 22). Separately, AWS does offer a proprietary 'shell access' default connector (\"Use Lambda-provided defaults for inbound port access (with JWE authentication), shell access, and public internet egress\", microvms-how-it-works.html) via its own JWE-token protocol — a remote shell mechanism, but not the SSH protocol — so the literal 'ssh' field is false while a non-SSH shell path does exist.",
   "checked": "2026-09-30"
  },
  "desktop": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "AWS Lambda MicroVMs are purpose-built for these use cases. They are serverless compute environments that provide VM-level isolation with full operating system capabilities... snapshot-based rapid startup speeds, and fine-grained control over ingress networking (port access, support for HTTP/2, gRPC, WebSockets) and egress networking",
   "note": "Product is a headless serverless compute/VM environment reached via HTTPS/API endpoints; no VNC/RDP/graphical desktop is described anywhere in the guide's Key features list (rapid startup, lifecycle control, flexible networking, flexible resource allocation) — outside the product's scope.",
   "checked": "2026-09-30"
  },
  "browser": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "If you're building an application where multiple users or AI agents connect to a compute environment and run code (for example, interactive development environments, CI/CD systems, or sandboxes for AI) – you need compute environments that start fast, stay isolated between tenants",
   "note": "No managed/preinstalled browser is mentioned; the service is a generic code-execution VM, not a browser product — outside the product's scope.",
   "checked": "2026-09-30"
  },
  "computer_use": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "Anthropic hosts the agent loop and Claude model, while the Lambda MicroVM is where your tool calls run.",
   "note": "Any computer-use/screenshot+click loop is run by a third party (e.g. Anthropic Claude, Cursor) that treats the MicroVM as a sandboxed backend; AWS itself ships no screenshot/click-driving API — outside the product's scope.",
   "checked": "2026-09-30"
  },
  "volumes": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "The only required parameter is --image-identifier (which must be the ARN of the MicroVM image). All other parameters are optional.",
   "note": "Full RunMicrovm parameter set (image, version, execution role, idle policy, max duration, run-hook payload, logging, ingress/egress connectors) has no volume/storage-attach parameter; only the root disk baked into the image snapshot is available.",
   "checked": "2026-09-30"
  },
  "public_ipv4": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "Every MicroVM gets a unique public HTTPS endpoint",
   "note": "Access is via a Lambda-managed HTTPS endpoint (DNS name + JWE auth token), not a dedicated public IPv4 address per machine; matches network.ipv4_available: false already on the card.",
   "checked": "2026-09-30"
  },
  "agent_harnesses": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-integrations-claude-managed-agents.html",
   "quote": "Anthropic hosts the agent loop and Claude model, while the Lambda MicroVM is where your tool calls run.",
   "note": "MicroVMs are documented as the underlying sandbox that third-party agent products (Claude Managed Agents, Cursor Cloud Agents, OpenAI Agents API) run their sandboxes on; AWS does not preinstall/offer any coding agent (Claude Code, Codex, OpenCode, etc.) as a template itself.",
   "checked": "2026-09-30"
  },
  "gpu": {
   "value": false,
   "source": "https://aws.amazon.com/lambda/pricing/",
   "quote": "Lambda MicroVMs pricing is based on the compute resources you use, snapshot read/write operations and storage, and data transfer at standard AWS rates. Compute Lambda MicroVMs eliminate the need to right-size each compute environment for peak activity. You configure a baseline by setting memory, and CPU is allocated proportionally.",
   "note": "Pricing page enumerates only vCPU/memory/snapshot/data-transfer meters; no GPU SKU or GPU option exists for MicroVMs (unlike EC2/SageMaker).",
   "checked": "2026-09-30"
  },
  "windows": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html",
   "quote": "Each MicroVM runs an Amazon Linux 2023 operating system with operating system capabilities, providing near-instant launch and resume.",
   "note": "Base image / guest OS is fixed to Amazon Linux 2023 — Linux only, no Windows option.",
   "checked": "2026-09-30"
  },
  "macos": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html",
   "quote": "Each MicroVM runs an Amazon Linux 2023 operating system with operating system capabilities, providing near-instant launch and resume.",
   "note": "Firecracker microVMs run Amazon Linux 2023 only; macOS is not offered (and Firecracker cannot virtualize macOS).",
   "checked": "2026-09-30"
  },
  "self_host": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "AWS Lambda MicroVMs are purpose-built for these use cases. They are serverless compute environments that provide VM-level isolation with full operating system capabilities... you need compute environments that start fast, stay isolated between tenants, and don't require you to manage servers or networking.",
   "note": "AWS Lambda MicroVMs is a fully-managed AWS control-plane service; there is no downloadable runtime/binary to run on your own infrastructure.",
   "checked": "2026-09-30"
  },
  "byoc": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "AWS Lambda MicroVMs are purpose-built for these use cases. They are serverless compute environments that provide VM-level isolation... and don't require you to manage servers or networking.",
   "note": "It is AWS's own multi-tenant service running in AWS-owned infrastructure (with optional VPC egress INTO your account's VPC for networking only); there is no mode where the whole MicroVMs control plane is deployed into a customer's own cloud account.",
   "checked": "2026-09-30"
  },
  "open_source": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "AWS Lambda MicroVMs deliver these core capabilities through Firecracker virtualization, which powers Lambda Functions' 15 trillion+ monthly invocations.",
   "note": "The underlying Firecracker VMM is open source, but the AWS Lambda MicroVMs product itself (control plane, APIs, billing, orchestration) is a closed, proprietary managed AWS service, not something you can download the full source of.",
   "checked": "2026-09-30"
  },
  "mcp_server": {
   "value": false,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-microvms-guide.html",
   "quote": "AWS Lambda MicroVMs are purpose-built for these use cases. They are serverless compute environments that provide VM-level isolation with full operating system capabilities...",
   "note": "No AWS-shipped MCP server for controlling Lambda MicroVMs was found across the guide, images, launching, networking, how-it-works, or the Claude/Cursor/OpenAI-Agents integration pages — those integration pages document only the lambda-microvms control-plane API (run/suspend/resume/terminate, image build) being called by third-party agent products, not an MCP tool surface. Prior research on this card notes only an unrelated 'AWS Lambda MicroVMs skill' for coding agents (dev tooling, not an MCP server).",
   "checked": "2026-09-30"
  },
  "cpu_class": {
   "value": {
    "on-demand-arm64": "shared",
    "on-demand-arm64-eu": "shared"
   },
   "source": "https://aws.amazon.com/lambda/pricing/",
   "quote": "Lambda MicroVMs eliminate the need to right-size each compute environment for peak activity. You configure a baseline by setting memory, and CPU is allocated in a 2:1 memory-to-CPU ratio – the default is 2GB / 1vCPU. During peak activity, your MicroVM can vertically scale up to 4x the baseline (up to 8GB / 4vCPU), with no action required on your part.",
   "note": "AWS never states the baseline vCPUs are dedicated/reserved cores; the model allocates vCPU proportionally to configured memory and lets the same MicroVM automatically burst up to 4x that baseline on the underlying (multi-tenant Firecracker host) hardware, billing extra only for consumed burst seconds — the same proportional, no-pinned-core allocation style AWS uses for classic Lambda functions. No published baseline-% figure exists (so not classifiable as burstable:NN); closest documented behavior is oversubscribed/shared vCPU, applied identically to both Arm64 pricing modes since the baseline-peak billing model is the same across regions.",
   "checked": "2026-09-30"
  },
  "usage_api": {
   "value": true,
   "source": "https://docs.aws.amazon.com/cost-management/latest/userguide/ce-filtering.html",
   "quote": "With Cost Explorer, you can filter how you view your AWS costs by one or more of the following: Resources (unique identifier for your resources), Service, or Tag. You can use Cost Explorer to see which service you use the most, which Availability Zone, or tag.",
   "note": "granularity: per-tag; cost: yes; AWS Lambda MicroVMs are billed through AWS Cost Explorer and AWS Cost and Usage Reports, both accessible via REST API (GetCostAndUsage), AWS SDK, and CLI with JSON output. MicroVMs can be tagged via the Lambda TagResource API (https://docs.aws.amazon.com/lambda/latest/api/API_TagResource.html) and filtered in Cost Explorer by tag or resource ID. Costs include compute (vCPU-seconds, GB-seconds), snapshot storage/read/write, and data transfer. Cost Explorer optionally supports resource-level granularity with per-resource identifier tracking.",
   "confidence": "high",
   "checked": "2026-10-01"
  },
  "persist_scope": {
   "value": "whole",
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-how-it-works.html",
   "quote": "SUSPENDING SUSPENDED /suspend hook completed, memory and disk state checkpointed. SUSPENDED RUNNING Traffic arrives (autoResumeEnabled=true) or explicit resume-microvm API call.",
   "note": "The whole disk survives a stop, installed packages included.",
   "checked": "2026-10-01"
  },
  "arm64": {
   "value": true,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html",
   "quote": "Lambda MicroVMs support the ARM64 (AWS Graviton) architecture.",
   "note": "Arm64 only. The pricing page MicroVMs section has a single \"Graviton (ARM)\" price table and its examples are \"using ARM (Graviton) architecture\". The x86 Lambda-MicroVM-vCPU-Second / Memory-GB-Second SKUs in the Price List API are not an offered architecture, so the two x86 modes were removed.",
   "checked": "2026-10-14"
  },
  "max_session_h": {
   "value": 8,
   "source": "https://docs.aws.amazon.com/lambda/latest/dg/microvms-launching.html",
   "quote": "The maximum total lifespan of the MicroVM, including both running and suspended time. Lambda terminates the MicroVM when this duration is exceeded. Range: 1–28,800 seconds (8 hours).",
   "note": "Quotas page (gettingstarted-limits.html): \"Maximum execution duration per MicroVM | 8 hours (28,800 seconds) | No\" (not adjustable).",
   "checked": "2026-10-14"
  }
 },
 "locations": [
  {
   "country": "US",
   "state": "VA",
   "city": "Ashburn",
   "provider_region": "us-east-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "US",
   "state": "OH",
   "city": "Columbus",
   "provider_region": "us-east-2",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "US",
   "state": "OR",
   "city": "Pendleton",
   "provider_region": "us-west-2",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "IE",
   "state": null,
   "city": "Dublin",
   "provider_region": "eu-west-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "SE",
   "state": null,
   "city": "Stockholm",
   "provider_region": "eu-north-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "DE",
   "state": null,
   "city": "Frankfurt",
   "provider_region": "eu-central-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "IN",
   "state": null,
   "city": "Mumbai",
   "provider_region": "ap-south-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "JP",
   "state": null,
   "city": "Tokyo",
   "provider_region": "ap-northeast-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "SG",
   "state": null,
   "city": "Singapore",
   "provider_region": "ap-southeast-1",
   "self_serve": true,
   "choosable": true
  },
  {
   "country": "AU",
   "state": null,
   "city": "Sydney",
   "provider_region": "ap-southeast-2",
   "self_serve": true,
   "choosable": true
  }
 ],
 "locations_source": "https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSLambda/current/region_index.json",
 "locations_quote": "Regions with MicroVM SKUs: us-east-1, us-east-2, us-west-2, eu-west-1, eu-north-1, eu-central-1, ap-south-1, ap-northeast-1, ap-southeast-1, ap-southeast-2.",
 "locations_checked": "2026-09-28"
}