AWS vpc: Clarify Route 53 naming and DNS resolution setting for resource gateway
Summary
Changes 'Route53 private hosted zone' to 'Route 53 private hosted zone' and rewrites the instruction to explicitly say to set 'DNS resolution' to IN_VPC when using a private DNS server or domain-name targets in a Route 53 private hosted zone.
Security assessment
The edit is a wording/product-name clarification that also names the DNS resolution mode (IN_VPC) for resolving private DNS targets; DNS resolution mode has indirect security impact (internal DNS resolution scope) but the change documents configuration rather than addressing a vulnerability.
Evidence
+ 1. If you are using a private DNS server or your domain-name targets are in a Route 53 private hosted zone, set DNS resolution to IN_VPC.
Diff
diff --git a/vpc/latest/privatelink/create-resource-gateway.md b/vpc/latest/privatelink/create-resource-gateway.md index 7e1693203..128362051 100644 --- a//vpc/latest/privatelink/create-resource-gateway.md +++ b//vpc/latest/privatelink/create-resource-gateway.md @@ -35 +35 @@ The default is 16 IPv4 addresses per ENI. This is a suitable number of IPs to fo - 1. If you are using a private DNS server or your domain-name targets are in a Route53 private hosted zone, set to IN_VPC + 1. If you are using a private DNS server or your domain-name targets are in a Route 53 private hosted zone, set DNS resolution to IN_VPC.