AWS whitepapers documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in multiple locations
Security assessment
The changes are purely terminology updates without modifying security characteristics. PrivateLink's security posture remains unchanged - this is a branding/style consistency update rather than a security-related modification.
Diff
diff --git a/whitepapers/latest/aws-privatelink/aws-privatelink.md b/whitepapers/latest/aws-privatelink/aws-privatelink.md index f4d813f9a..140ad71aa 100644 --- a//whitepapers/latest/aws-privatelink/aws-privatelink.md +++ b//whitepapers/latest/aws-privatelink/aws-privatelink.md @@ -15 +15 @@ Publication date: **June 3, 2021** ([Document revisions](./document-revisions.ht -Amazon Virtual Private Cloud (Amazon VPC) gives AWS customers the ability to define a virtual private network within the AWS Cloud. Customers can build services securely within an Amazon VPC and provide access to these services internally and externally using traditional methods such as an internet gateway, VPC peering, network address translation (NAT), a virtual private network (VPN), and AWS Direct Connect. This whitepaper presents how AWS PrivateLink keeps network traffic private and allows connectivity from Amazon VPCs to services and data hosted on AWS in a secure and scalable manner. +Amazon Virtual Private Cloud (Amazon VPC) gives AWS customers the ability to define a virtual private network within the AWS Cloud. Customers can build services securely within an Amazon VPC and provide access to these services internally and externally using traditional methods such as an internet gateway, VPC peering, network address translation (NAT), a virtual private network (VPN), and Direct Connect. This whitepaper presents how AWS PrivateLink keeps network traffic private and allows connectivity from Amazon VPCs to services and data hosted on AWS in a secure and scalable manner. @@ -27 +27 @@ For more expert guidance and best practices for your cloud architecture—refere -The introduction of Amazon Virtual Private Cloud (Amazon VPC) in 2009 made it possible for customers to provision a logically-isolated section of the AWS cloud and launch AWS resources in a virtual network that they define. Traditional methods to access third-party applications or public AWS services from an Amazon VPC include using an internet gateway, virtual private network (VPN), AWS Direct Connect with a virtual private gateway, and VPC peering. +The introduction of Amazon Virtual Private Cloud (Amazon VPC) in 2009 made it possible for customers to provision a logically-isolated section of the AWS cloud and launch AWS resources in a virtual network that they define. Traditional methods to access third-party applications or public AWS services from an Amazon VPC include using an internet gateway, virtual private network (VPN), Direct Connect with a virtual private gateway, and VPC peering. @@ -72 +72 @@ A Transit VPC connects multiple Amazon Virtual Private Clouds that might be geog -AWS PrivateLink gives on-premises networks private access to AWS services via AWS Direct Connect. Customers can more easily migrate traditional on-premises applications to services hosted in the cloud and use cloud services with the confidence that traffic remains private. +AWS PrivateLink gives on-premises networks private access to AWS services via Direct Connect. Customers can more easily migrate traditional on-premises applications to services hosted in the cloud and use cloud services with the confidence that traffic remains private.