AWS fsx documentation change
Summary
Updated documentation to replace 'AWS Direct Connect' with 'Direct Connect' in VPC endpoint explanation
Security assessment
The change is a minor terminology adjustment (brand name shortening) without altering security context. The security posture description about private access via VPC endpoints remains unchanged.
Diff
diff --git a/fsx/latest/ONTAPGuide/fsx-vpc-endpoints.md b/fsx/latest/ONTAPGuide/fsx-vpc-endpoints.md index aebec68b8..6406ca91a 100644 --- a//fsx/latest/ONTAPGuide/fsx-vpc-endpoints.md +++ b//fsx/latest/ONTAPGuide/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.