FSX access from Public IP range in a private network

Question

If a client is using a public IP range in their private on-premises network, is there any built in FSX functionality or security that blocks this connection based on the fact that the IP range is a public address range?   The connection is site-to-site VPN from On Premises to VPC.  Ping and RDP work with the Public IP range over the site-to-site VPN.    FSX is working fine over separate AWS direct connect from a different site, using a private non-routable IP range.

Answer

I think I may have found the answer to my own question.

Amazon FSx now supports on-premises access from additional IP address ranges
Posted On: Dec 17, 2020

Amazon FSx, a fully managed service that makes it easy to launch and run feature-rich and highly-performant file systems, today announced that customers can now access Amazon FSx for Windows File Server and Amazon FSx for Lustre file systems from non-RFC1918 IP addresses. Starting today, Amazon FSx for Windows File Server customers can now also join their file systems to on-premises Active Directories with non-RFC1918 IP addresses.

Amazon FSx file systems are accessible from within the AWS Virtual Private Cloud (VPC) in which they’re created, as well as from peered and on-premises networks using AWS VPC Peering, AWS Direct Connect, or AWS VPN. Before today, access from peered or on-premises networks was limited to networks that use an RFC1918 IP address range (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). Today’s launch provides Amazon FSx customers with even more flexibility in how they access their file storage by expanding support for access from any peered or on-premises network.

All newly-created Amazon FSx file systems can now be accessed from any peered or on-premises network range without any additional setup required. For more information on Amazon FSx, please visit the Amazon FSx product page.

FSX access from Public IP range in a private network

Relevant content