AWS lambda: MicroVM example uses HTTP_INGRESS instead of ALL_INGRESS
Summary
The getting-started run-microvm example now attaches the HTTP_INGRESS network connector rather than ALL_INGRESS, and the auth token header example placeholder was changed from `<token-value>` to `token-value`.
Security assessment
Switching the sample ingress connector from ALL_INGRESS to HTTP_INGRESS demonstrates a narrower, least-privilege network exposure for MicroVMs, reducing the surface reachable from the network; no specific vulnerability or CVE is referenced.
Evidence
+ --ingress-network-connectors "arn:aws:lambda:us-east-1:aws:network-connector:aws-network-connector:HTTP_INGRESS" \
Diff
diff --git a/lambda/latest/dg/microvms-getting-started.md b/lambda/latest/dg/microvms-getting-started.md index a91e8ad..05af437 100644 --- a//lambda/latest/dg/microvms-getting-started.md +++ b//lambda/latest/dg/microvms-getting-started.md @@ -155 +155 @@ Run a MicroVM with the following command: - --ingress-network-connectors "arn:aws:lambda:us-east-1:aws:network-connector:aws-network-connector:ALL_INGRESS" \ + --ingress-network-connectors "arn:aws:lambda:us-east-1:aws:network-connector:aws-network-connector:HTTP_INGRESS" \ @@ -200 +200 @@ The response includes a token in the `authToken` field. Use it to send a request - -H "X-aws-proxy-auth: <token-value>" + -H "X-aws-proxy-auth: token-value"