shiichan

S3 File Gateway's FIPS Traffic Can Now Stay Fully Private!

Hi, it's me, Shiichan! Today's news is for anyone dealing with regulated workloads.

AWS What's New aws.amazon.com

What was announced?

AWS What's New announced that AWS Storage Gateway now supports FIPS 140-3 validated endpoints over AWS PrivateLink for Amazon S3 File Gateway.

The story so far

Until now, FIPS endpoints for File Gateway were only available over the public internet. For regulated workloads that want to keep traffic on a private network as much as possible, that was a quietly annoying limitation.

What changes

With this update, you can keep FIPS-compliant traffic entirely on the private AWS network. Concretely, that means:

  • File Gateway can reach Storage Gateway service endpoints privately through a FIPS interface VPC endpoint in your VPC
  • NFS and SMB file shares can reach Amazon S3 through an S3 FIPS interface endpoint
  • Your end-to-end file transfer workload can run on FIPS-compliant private connectivity throughout

Dive Deep

To get started, create FIPS interface endpoints for Storage Gateway and Amazon S3 in your VPC, then choose the FIPS VPC endpoint option when activating your gateway and configuring your file shares. To activate a gateway with a FIPS PrivateLink endpoint, your gateway needs software version 2.1.10 or later.

This is available in the eight AWS regions where Storage Gateway offers FIPS endpoints:

  • US East (N. Virginia)
  • US East (Ohio)
  • US West (N. California)
  • US West (Oregon)
  • Canada (Central)
  • Canada West (Calgary)
  • AWS GovCloud (US-East)
  • AWS GovCloud (US-West)

Wrap-up

  • AWS Storage Gateway now supports FIPS 140-3 validated endpoints over PrivateLink for S3 File Gateway.
  • FIPS-compliant traffic that used to require the public internet can now stay entirely private.
  • Gateway software version 2.1.10 or later is required to use it.
  • It's available across eight regions in the US, Canada, and GovCloud.
  • A quiet but genuinely useful upgrade for infrastructure teams running regulated file-transfer workloads.