AWS Security ChangesHomeSearch

AWS lambda: Fix region placeholder formatting in MicroVM endpoint hostnames

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

File: lambda/latest/dg/microvms-networking.md

Summary

Corrected the example MicroVM endpoint hostnames so the region placeholder is rendered as `us-east-1` inside the code span in two places.

Security assessment

This is a documentation formatting correction for the private-link endpoint hostname examples; the surrounding text about private DNS and interface endpoints is unchanged and no new security control is introduced.

Evidence

+To keep HTTPS traffic to your running MicroVMs private, create an interface endpoint for the `com.amazonaws.`region`.lambda-microvm` service. This endpoint handles connections to MicroVM endpoint URLs (for example, `abc123def456.lambda-microvm.`us-east-1`.on.aws`).

Diff

diff --git a/lambda/latest/dg/microvms-networking.md b/lambda/latest/dg/microvms-networking.md
index f9b9775..9b456b0 100644
--- a//lambda/latest/dg/microvms-networking.md
+++ b//lambda/latest/dg/microvms-networking.md
@@ -290 +290 @@ The following example policy allows user `MyUser` to list and get MicroVM images
-To keep HTTPS traffic to your running MicroVMs private, create an interface endpoint for the `com.amazonaws.`region`.lambda-microvm` service. This endpoint handles connections to MicroVM endpoint URLs (for example, `abc123def456.lambda-microvm.us-east-1.on.aws`).
+To keep HTTPS traffic to your running MicroVMs private, create an interface endpoint for the `com.amazonaws.`region`.lambda-microvm` service. This endpoint handles connections to MicroVM endpoint URLs (for example, `abc123def456.lambda-microvm.`us-east-1`.on.aws`).
@@ -339 +339 @@ To verify that the endpoint is available and that private DNS is in effect:
-**When private DNS is enabled** – The endpoint manages DNS resolution for `*.lambda-microvm.`region`.on.aws` inside your VPC. Your existing MicroVM endpoint hostnames (for example, `abc123def456.lambda-microvm.us-east-1.on.aws`) resolve to the private IP addresses of the endpoint network interfaces. No client change is required.
+**When private DNS is enabled** – The endpoint manages DNS resolution for `*.lambda-microvm.`region`.on.aws` inside your VPC. Your existing MicroVM endpoint hostnames (for example, `abc123def456.lambda-microvm.`us-east-1`.on.aws`) resolve to the private IP addresses of the endpoint network interfaces. No client change is required.