AWS fsx documentation change
Summary
Replaced 'AWS Direct Connect' with 'Direct Connect' in the VPC endpoint security description.
Security assessment
Change is a minor terminology update in existing security documentation. The security posture description about private network traffic remains identical. No new security features or vulnerabilities are addressed.
Diff
diff --git a/fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md b/fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md index 3e0536201..36dd87ea0 100644 --- a//fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md +++ b//fsx/latest/OpenZFSGuide/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/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/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.