AWS Route53 documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' and simplified 'virtual private gateway' to 'virtual gateway'
Security assessment
Both changes are terminology updates and documentation clarifications. The 'virtual gateway' simplification doesn't alter security configurations or introduce new security considerations.
Diff
diff --git a/Route53/latest/DeveloperGuide/resolver.md b/Route53/latest/DeveloperGuide/resolver.md index f4d29ebde..7431686a6 100644 --- a//Route53/latest/DeveloperGuide/resolver.md +++ b//Route53/latest/DeveloperGuide/resolver.md @@ -51 +51 @@ The diagram illustrates the following steps: - 4. The outbound endpoint forwards the query to the on-premises DNS resolver through a private connection between AWS and the data center. The connection can be either AWS Direct Connect or AWS Site-to-Site VPN, depicted as a virtual private gateway. + 4. The outbound endpoint forwards the query to the on-premises DNS resolver through a private connection between AWS and the data center. The connection can be either Direct Connect or AWS Site-to-Site VPN, depicted as a virtual private gateway. @@ -64 +64 @@ The diagram illustrates the following steps: - 3. The query arrives at the inbound endpoint through a private connection, such as AWS Direct Connect or AWS Site-to-Site VPN, depicted as a virtual gateway. + 3. The query arrives at the inbound endpoint through a private connection, such as Direct Connect or AWS Site-to-Site VPN, depicted as a virtual gateway.