Amazon FSx now supports AWS PrivateLink
You can now use [AWS PrivateLink](/privatelink/) to privately access the [Amazon FSx Application Programming Interface (Amazon FSx API)](https://docs.aws.amazon.com/fsx/latest/APIReference/welcome.html) from your [Amazon Virtual Private Cloud (Amazon VPC)](/vpc/) without using public IPs, and without requiring the traffic to traverse across the Internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and your on-premises networks, without exposing your traffic to the public internet. You can now manage your Amazon FSx file systems using the Amazon FSx API without requiring an Internet Gateway in your VPC, instead using AWS PrivateLink with private IP connectivity and security groups to help meet your compliance requirements. The Amazon FSx API is a webservice that enables you to set up, operate, scale, and backup your Amazon FSx file systems programmatically via [AWS Software Development Kits](/tools/) (SDKs). With today’s launch, by using AWS PrivateLink you can invoke management operations using the Amazon FSx API, while significantly simplifying your internal network architecture. You no longer need to use an Internet Gateway, Network Address Translation (NAT) devices, or firewall proxies to connect to the Amazon FSx API. To use AWS PrivateLink, create an [interface VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/endpoint-services-overview.html) for Amazon FSx in your VPC using the Amazon VPC console, SDK, or CLI. You can also access the VPC endpoint from on-premises environments or from other VPCs using AWS VPN, AWS Direct Connect, or VPC Peering. This feature is available in all regions where [Amazon FSx is available](/about-aws/global-infrastructure/regional-product-services/). To learn more, visit the [Amazon FSx product page](/fsx/), read the FSx VPC endpoint documentation, or get started in the [AWS Console](https://console.aws.amazon.com/vpc/home).