AWS whitepapers documentation change
Summary
Updated service name from 'AWS Direct Connect' to 'Direct Connect' in DNS configuration context
Security assessment
Change involves branding/naming convention adjustment (removing 'AWS' prefix) without altering technical security guidance or addressing vulnerabilities.
Diff
diff --git a/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/dns.md b/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/dns.md index ccf33efc6..8636f972a 100644 --- a//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/dns.md +++ b//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/dns.md @@ -15 +15 @@ If you want to map your instances to a custom domain name, you can use [Amazon R -DNS is a critical component of any infrastructure, hybrid or otherwise, as it provides the hostname-to-IP-address resolution that applications rely on. Customers implementing hybrid environments usually have a DNS resolution system already in place, and they want a DNS solution that works in tandem with their current system. Native Route 53 resolver (+2 offset of the base VPC CIDR) is not reachable from on-premises networks using VPN or AWS Direct Connect. Therefore, when you integrate DNS for the VPCs in an AWS Region with DNS for your network, you need a Route 53 Resolver inbound endpoint (for DNS queries that you are forwarding to your VPCs) and a Route 53 Resolver outbound endpoint (for queries that you are forwarding from your VPCs to your network). +DNS is a critical component of any infrastructure, hybrid or otherwise, as it provides the hostname-to-IP-address resolution that applications rely on. Customers implementing hybrid environments usually have a DNS resolution system already in place, and they want a DNS solution that works in tandem with their current system. Native Route 53 resolver (+2 offset of the base VPC CIDR) is not reachable from on-premises networks using VPN or Direct Connect. Therefore, when you integrate DNS for the VPCs in an AWS Region with DNS for your network, you need a Route 53 Resolver inbound endpoint (for DNS queries that you are forwarding to your VPCs) and a Route 53 Resolver outbound endpoint (for queries that you are forwarding from your VPCs to your network).