AWS Route53 documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for branding consistency
Security assessment
This is a minor branding/naming change without technical or security implications to the documented connectivity requirements
Diff
diff --git a/Route53/latest/DeveloperGuide/resolver-forwarding-inbound-queries.md b/Route53/latest/DeveloperGuide/resolver-forwarding-inbound-queries.md index a1bf0c770..45e46b5f8 100644 --- a//Route53/latest/DeveloperGuide/resolver-forwarding-inbound-queries.md +++ b//Route53/latest/DeveloperGuide/resolver-forwarding-inbound-queries.md @@ -7 +7 @@ -To forward DNS queries from your network to Resolver, you create an inbound endpoint. An inbound endpoint specifies the IP addresses (from the range of IP addresses available to your VPC) that you want DNS resolvers on your network to forward DNS queries to. Those IP addresses aren't public IP addresses, so for each inbound endpoint, you need to connect your VPC to your network using either an AWS Direct Connect connection or a VPN connection. +To forward DNS queries from your network to Resolver, you create an inbound endpoint. An inbound endpoint specifies the IP addresses (from the range of IP addresses available to your VPC) that you want DNS resolvers on your network to forward DNS queries to. Those IP addresses aren't public IP addresses, so for each inbound endpoint, you need to connect your VPC to your network using either an Direct Connect connection or a VPN connection.