AWS vpc-lattice documentation change
Summary
Added DNS resolution configuration step during resource gateway creation, specifying IN_VPC option for private DNS scenarios
Security assessment
Introduces DNS resolution configuration (IN_VPC option) which enhances security by enabling private DNS resolution for internal resources, preventing public DNS exposure. No evidence of addressing a specific vulnerability.
Diff
diff --git a/vpc-lattice/latest/ug/create-resource-gateway.md b/vpc-lattice/latest/ug/create-resource-gateway.md index 0f91d3cf3..8b635da42 100644 --- a//vpc-lattice/latest/ug/create-resource-gateway.md +++ b//vpc-lattice/latest/ug/create-resource-gateway.md @@ -31 +31 @@ The default is 16 IPv4 addresses per ENI. This is a suitable number of IPs to fo - 8. (Optional) To add a tag, choose **Add new tag** and enter the tag key and the tag value. + 8. For **Resource Config DNS Resolution** , choose how you want DNS to be resolved for domain-name targets. @@ -33 +33,5 @@ The default is 16 IPv4 addresses per ENI. This is a suitable number of IPs to fo - 9. Choose **Create resource gateway**. + 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 + + 9. (Optional) To add a tag, choose **Add new tag** and enter the tag key and the tag value. + + 10. Choose **Create resource gateway**.