AWS AmazonS3 medium security documentation change
Summary
Multiple changes including terminology updates ('AWS VPN' to 'Site-to-Site VPN'), added note about hybrid post-quantum TLS unsupported, URL formatting fixes, and VPN terminology consistency
Security assessment
The addition of 'Hybrid post-quantum Transport Layer Security (TLS)' to the unsupported features list directly documents a security-related limitation. This indicates awareness of cryptographic security considerations related to quantum computing threats.
Diff
diff --git a/AmazonS3/latest/userguide/privatelink-interface-endpoints.md b/AmazonS3/latest/userguide/privatelink-interface-endpoints.md index ba521c811..736a75918 100644 --- a//AmazonS3/latest/userguide/privatelink-interface-endpoints.md +++ b//AmazonS3/latest/userguide/privatelink-interface-endpoints.md @@ -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 [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 (Site-to-Site 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). @@ -78,0 +79,2 @@ Interface endpoints for Amazon S3 does not support the following: + * Hybrid post-quantum Transport Layer Security (TLS) + @@ -180 +182 @@ To take advantage of the lowest cost network path when using **Enable private DN -If you want to update an existing interface endpoint to **Enable private DNS only for inbound endpoints** , first confirm that your VPC has an S3 gateway endpoint. For more information about gateway endpoints and managing private DNS names, see [Gateway VPC endpoints](https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-gateway.html) and [Manage DNS names](https://docs.aws.amazon.com/vpc/latest/privatelink/manage-dns-names.html) respectively in the _AWS PrivateLink Guide_. +If you want to update an existing interface endpoint to **Enable private DNS only for inbound endpoints** , first confirm that your VPC has an S3 gateway endpoint. For more information about gateway endpoints and managing private DNS names, see [Gateway VPC endpoints](https://docs.aws.amazon.com//vpc/latest/privatelink/vpce-gateway.html) and [Manage DNS names](https://docs.aws.amazon.com//vpc/latest/privatelink/manage-dns-names.html) respectively in the _AWS PrivateLink Guide_. @@ -186 +188 @@ The **Enable private DNS only for inbound endpoints** option is available only f -For more information about creating a VPC endpoint that uses **Enable private DNS only for inbound endpoints** , see [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html) in the _AWS PrivateLink Guide_. +For more information about creating a VPC endpoint that uses **Enable private DNS only for inbound endpoints** , see [Create an interface endpoint](https://docs.aws.amazon.com//vpc/latest/privatelink/create-interface-endpoint.html) in the _AWS PrivateLink Guide_. @@ -285 +287 @@ Replace the ARN ``us-east-1:123456789012:accesspoint/accesspointexamplename``, t -If you can't run the command successfully, update your AWS CLI to the latest version and try again. For more information on the update instructions, see [ Installing or updating the latest version of the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html#getting-started-install-instructions) in the _AWS Command Line Interface User Guide_. +If you can't run the command successfully, update your AWS CLI to the latest version and try again. For more information on the update instructions, see [ Installing or updating the latest version of the AWS CLI](https://docs.aws.amazon.com//cli/latest/userguide/getting-started-install.html#getting-started-install-instructions) in the _AWS Command Line Interface User Guide_. @@ -446 +448 @@ The diagram illustrates the following: - * Your on-premises network uses Direct Connect or AWS VPN to connect to VPC A. + * Your on-premises network uses Direct Connect or Site-to-Site VPN to connect to VPC A. @@ -450 +452 @@ The diagram illustrates the following: - * 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. + * On-premises applications send data to the interface endpoint in the VPC through Direct Connect (or Site-to-Site VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network. @@ -465 +467 @@ The diagram illustrates the following: - * 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. + * On-premises applications use endpoint-specific DNS names to send data to the interface endpoint within the VPC through Direct Connect (or Site-to-Site VPN). AWS PrivateLink moves the data from the interface endpoint to Amazon S3 over the AWS network.