AWS Storage Gateway now supports FIPS-compliant private connectivity for Amazon S3 File Gateway

AWS Storage Gateway FIPS 140-3 Support Over AWS PrivateLink
AWS Storage Gateway now supports FIPS 140-3 validated endpoints over AWS PrivateLink for Amazon S3 File Gateway. This update allows FIPS-compliant traffic to stay on the private AWS network, facilitating its use for regulated workloads.
With this launch, File Gateway can connect to Storage Gateway service endpoints privately through a FIPS interface VPC endpoint in your VPC. You can also create NFS and SMB file shares that connect to Amazon S3 through an S3 FIPS interface endpoint, enabling FIPS-compliant private connectivity for end-to-end file transfer workloads.
What to do
- Create FIPS interface endpoints for Storage Gateway and Amazon S3 in your VPC.
- Choose the FIPS VPC endpoint option when activating your gateway and configuring your file shares.
- Ensure your gateway is running software version 2.1.10 or later to activate a gateway with a FIPS PrivateLink endpoint.
This launch is available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), Canada West (Calgary), AWS GovCloud (US-East), and AWS GovCloud (US-West).
Source: AWS release notes
If you need further guidance on AWS, our experts are available at AWS@westloop.io. You may also reach us by submitting the Contact Us form.



