AWS fsx documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for service name consistency
Security assessment
The edit maintains existing security documentation about VPC endpoints and PrivateLink without adding new security features or addressing vulnerabilities. The security posture description remains unchanged.
Diff
diff --git a/fsx/latest/FileCacheGuide/vpc-endpoints.md b/fsx/latest/FileCacheGuide/vpc-endpoints.md index 58412d7d0..6396af96d 100644 --- a//fsx/latest/FileCacheGuide/vpc-endpoints.md +++ b//fsx/latest/FileCacheGuide/vpc-endpoints.md @@ -9 +9 @@ Considerations for Amazon File Cache interface VPC endpointsCreating an interfac -You can improve the security posture of your VPC by configuring Amazon File Cache 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 AWS 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 AWS 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 File Cache 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 AWS 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 AWS APIs. Traffic between your VPC and Amazon FSx does not leave the AWS network.