- Newest
- Most votes
- Most comments
You can access an FSx for Lustre file system from clients in a different VPC by using VPC peering or transit gateways. These networking connections allow compute instances in one VPC to access Amazon FSx file systems in another VPC, even if the VPCs belong to different AWS accounts or are in different AWS Regions.
For DNS resolution across VPCs, you need to ensure that:
-
The
enableDnsHostnamesandenableDnsSupportattributes are set on your VPC. These settings are required for proper DNS resolution. -
After setting up a VPC peering or transit gateway connection, you should be able to access your file system using its DNS name (fs-<id>.fsx.<region>.amazonaws.com) just as you would from compute instances within the associated VPC.
For more secure access, you can also use interface VPC endpoints (powered by AWS PrivateLink) for Amazon FSx API operations. This allows instances in your VPC to communicate with Amazon FSx APIs without requiring public IP addresses.
If you're implementing a centralized DNS solution, you may need to configure DNS forwarding between your VPCs to ensure that the FSx DNS names can be resolved across your network. This would allow your HPC cluster using AWS ParallelCluster to properly resolve the FSx Lustre file system's DNS name.
Sources
Accessing your data - Amazon FSx for Windows File Server
Amazon FSx for Lustre and interface VPC endpoints (AWS PrivateLink) - FSx for Lustre
Amazon FSx for Windows File Server and interface VPC endpoints - Amazon FSx for Windows File Server
Relevant content
- AWS OFFICIALUpdated 2 years ago
