AWS fsx documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint security context
Security assessment
Terminology update in existing security documentation. While the paragraph discusses security posture, the change itself does not introduce new security information or address vulnerabilities.
Diff
diff --git a/fsx/latest/LustreGuide/fsx-vpc-endpoints.md b/fsx/latest/LustreGuide/fsx-vpc-endpoints.md index 169aa9dea..bd6c01331 100644 --- a//fsx/latest/LustreGuide/fsx-vpc-endpoints.md +++ b//fsx/latest/LustreGuide/fsx-vpc-endpoints.md @@ -9 +9 @@ Considerations for Amazon FSx interface VPC endpointsCreating an interface VPC e -You can improve the security posture of your VPC by configuring Amazon FSx to use an interface VPC endpoint. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon FSx 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 Amazon FSx APIs. Traffic between your VPC and Amazon FSx does not leave the AWS network. +You can improve the security posture of your VPC by configuring Amazon FSx to use an interface VPC endpoint. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access Amazon FSx 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 Amazon FSx APIs. Traffic between your VPC and Amazon FSx does not leave the AWS network.