AWS lake-formation documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
Minor terminology update aligning with product naming conventions. The change does not alter security guidance or address vulnerabilities - the security context of using PrivateLink remains unchanged.
Diff
diff --git a/lake-formation/latest/dg/privatelink.md b/lake-formation/latest/dg/privatelink.md index f2bddf44e..96f2f423b 100644 --- a//lake-formation/latest/dg/privatelink.md +++ b//lake-formation/latest/dg/privatelink.md @@ -13 +13 @@ If you use Amazon Virtual Private Cloud (Amazon VPC) to host your AWS resources, -You can establish a private connection between your VPC and AWS Lake Formation by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Lake Formation APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Lake Formation APIs. Traffic between your VPC and Lake Formation does not leave the Amazon network. +You can establish a private connection between your VPC and AWS Lake Formation by creating an _interface VPC endpoint_. Interface endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Lake Formation APIs without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Lake Formation APIs. Traffic between your VPC and Lake Formation does not leave the Amazon network.