AWS Route53 documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network connection options
Security assessment
The change appears to be a branding/terminology update rather than addressing security concerns. No security implications or vulnerability fixes are mentioned in the context.
Diff
diff --git a/Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.md b/Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.md index fbbb11f58..673dc1156 100644 --- a//Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.md +++ b//Route53/latest/DeveloperGuide/resolver-forwarding-outbound-queries.md @@ -12 +12 @@ To forward DNS queries that originate on Amazon EC2 instances in one or more VPC -To forward DNS queries from your VPCs to your network, you create an outbound endpoint. An outbound endpoint specifies the IP addresses that queries originate from. Those IP addresses, which you choose from the range of IP addresses available to your VPC, aren't public IP addresses. This means that, for each outbound endpoint, you need to connect your VPC to your network using AWS Direct Connect connection, a VPN connection, or a network address translation (NAT) gateway. Note that you can use the same outbound endpoint for multiple VPCs in the same Region, or you can create multiple outbound endpoints. If you want your outbound endpoint to use DNS64, you can enable DNS64 using Amazon Virtual Private Cloud. For more information, see [DNS64 and NAT64](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html#nat-gateway-nat64-dns64) in the _Amazon VPC User Guide_. +To forward DNS queries from your VPCs to your network, you create an outbound endpoint. An outbound endpoint specifies the IP addresses that queries originate from. Those IP addresses, which you choose from the range of IP addresses available to your VPC, aren't public IP addresses. This means that, for each outbound endpoint, you need to connect your VPC to your network using Direct Connect connection, a VPN connection, or a network address translation (NAT) gateway. Note that you can use the same outbound endpoint for multiple VPCs in the same Region, or you can create multiple outbound endpoints. If you want your outbound endpoint to use DNS64, you can enable DNS64 using Amazon Virtual Private Cloud. For more information, see [DNS64 and NAT64](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html#nat-gateway-nat64-dns64) in the _Amazon VPC User Guide_.