AWS vpc documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in gateway endpoint limitations.
Security assessment
Consistent branding update without security implications. No vulnerability or security feature mentioned.
Diff
diff --git a/vpc/latest/privatelink/vpc-endpoints-s3.md b/vpc/latest/privatelink/vpc-endpoints-s3.md index db914e4d0..8e9c53e92 100644 --- a//vpc/latest/privatelink/vpc-endpoints-s3.md +++ b//vpc/latest/privatelink/vpc-endpoints-s3.md @@ -50 +50 @@ Amazon S3 supports both gateway endpoints and interface endpoints. With a gatewa - * Endpoint connections cannot be extended out of a VPC. Resources on the other side of a VPN connection, VPC peering connection, transit gateway, or AWS Direct Connect connection in your VPC cannot use a gateway endpoint to communicate with Amazon S3. + * Endpoint connections cannot be extended out of a VPC. Resources on the other side of a VPN connection, VPC peering connection, transit gateway, or Direct Connect connection in your VPC cannot use a gateway endpoint to communicate with Amazon S3.