AWS AmazonS3 documentation change
Summary
Multiple updates replacing 'AWS Direct Connect' with 'Direct Connect' and adjusting documentation links
Security assessment
These changes standardize service naming conventions and update link text. The security aspects of PrivateLink (keeping traffic on AWS network, private connectivity) remain unchanged. No new security features or vulnerabilities addressed.
Diff
diff --git a/AmazonS3/latest/userguide/privatelink-interface-endpoints.md b/AmazonS3/latest/userguide/privatelink-interface-endpoints.md index df2dab893..ba521c811 100644 --- a//AmazonS3/latest/userguide/privatelink-interface-endpoints.md +++ b//AmazonS3/latest/userguide/privatelink-interface-endpoints.md @@ -9 +9 @@ Types of VPC endpointsRestrictions and limitations of AWS PrivateLink for Amazon -With AWS PrivateLink for Amazon S3, you can provision _interface VPC endpoints_ (interface endpoints) in your virtual private cloud (VPC). These endpoints are directly accessible from applications that are on premises over VPN and AWS Direct Connect, or in a different AWS Region over VPC peering. +With AWS PrivateLink for Amazon S3, you can provision _interface VPC endpoints_ (interface endpoints) in your virtual private cloud (VPC). These endpoints are directly accessible from applications that are on premises over VPN and Direct Connect, or in a different AWS Region over VPC peering. @@ -11 +11 @@ With AWS PrivateLink for Amazon S3, you can provision _interface VPC endpoints_ -Interface endpoints are represented by one or more elastic network interfaces (ENIs) that are assigned private IP addresses from subnets in your VPC. Requests to Amazon S3 over interface endpoints stay on the Amazon network. You can also access interface endpoints in your VPC from on-premises applications through AWS Direct Connect or AWS Virtual Private Network (AWS VPN). For more information about how to connect your VPC with your on-premises network, see the [AWS Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) and the [AWS Site-to-Site VPN User Guide](https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html). +Interface endpoints are represented by one or more elastic network interfaces (ENIs) that are assigned private IP addresses from subnets in your VPC. Requests to Amazon S3 over interface endpoints stay on the Amazon network. You can also access interface endpoints in your VPC from on-premises applications through AWS Direct Connect or AWS Virtual Private Network (AWS VPN). For more information about how to connect your VPC with your on-premises network, see the [Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/Welcome.html) and the [AWS Site-to-Site VPN User Guide](https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html). @@ -446 +446 @@ The diagram illustrates the following: - * Your on-premises network uses AWS Direct Connect or AWS VPN to connect to VPC A. + * Your on-premises network uses Direct Connect or AWS VPN to connect to VPC A. @@ -450 +450 @@ The diagram illustrates the following: - * On-premises applications send data to the interface endpoint in the VPC through AWS Direct Connect (or AWS VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network. + * On-premises applications send data to the interface endpoint in the VPC through Direct Connect (or AWS VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network. @@ -465 +465 @@ The diagram illustrates the following: - * On-premises applications use endpoint-specific DNS names to send data to the interface endpoint within the VPC through AWS Direct Connect (or AWS VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network. + * On-premises applications use endpoint-specific DNS names to send data to the interface endpoint within the VPC through Direct Connect (or AWS VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network.