AWS Security ChangesHomeSearch

AWS fsx documentation change

Service: fsx · 2025-11-22 · Documentation low

File: fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md

Summary

Fixed duplicate URL in AWS PrivateLink reference

Security assessment

The change corrects a broken URL but does not introduce new security content or address vulnerabilities. The security context about VPC endpoints remains unchanged.

Diff

diff --git a/fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md b/fsx/latest/OpenZFSGuide/fsx-vpc-endpoints.md
index 36dd87ea0..0461d883f 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 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.