AWS lambda: Cursor self-hosted worker example narrows ingress to HTTP_INGRESS
Summary
The description of the reference spawn.sh now says it attaches HTTP_INGRESS (instead of ALL_INGRESS) for image hooks, keeping INTERNET_EGRESS for the control plane.
Security assessment
The change documents a more restrictive ingress connector (HTTP_INGRESS rather than ALL_INGRESS) for worker image hooks, limiting inbound network exposure; it is hardening guidance rather than a fix for a specific reported vulnerability.
Evidence
+The reference `spawn.sh` attaches the managed `INTERNET_EGRESS` connector so the worker can reach Cursor's control plane, and `HTTP_INGRESS` for the image hooks. Outbound-only workers never receive inbound HTTPS after boot.
Diff
diff --git a/lambda/latest/dg/microvms-integrations-cursor-self-hosted-machines.md b/lambda/latest/dg/microvms-integrations-cursor-self-hosted-machines.md index 72e7cb9..af7a2aa 100644 --- a//lambda/latest/dg/microvms-integrations-cursor-self-hosted-machines.md +++ b//lambda/latest/dg/microvms-integrations-cursor-self-hosted-machines.md @@ -127 +127 @@ Keep the stack's `PoolNames` and the image's `POOL_NAME` aligned so the controll -The reference `spawn.sh` attaches the managed `INTERNET_EGRESS` connector so the worker can reach Cursor's control plane, and `ALL_INGRESS` for the image hooks. Outbound-only workers never receive inbound HTTPS after boot. +The reference `spawn.sh` attaches the managed `INTERNET_EGRESS` connector so the worker can reach Cursor's control plane, and `HTTP_INGRESS` for the image hooks. Outbound-only workers never receive inbound HTTPS after boot.