re:Invent is a builder conference. Every booth, chalk talk, and keynote makes the same point: AWS sells the parts, and you put them together. Usually that works out fine. For managed file transfer it usually doesn’t. Transfer Family plus Lambda plus Step Functions plus a home-built audit screen on CloudWatch costs more, breaks more, and eats more engineering time than anyone expects — and the partner-onboarding team still doesn’t get a real product out of it.
Files.com is on the floor because we’re the put-together version: managed file transfer on top of S3, with SFTP, AS2, FTPS, WebDAV, share links, inboxes, automations, partner onboarding, permissions, and audit already wired in. The native Amazon S3 integration connects your bucket as a Files.com folder or runs scheduled syncs in either direction — the data never leaves your bucket.
Here’s the bigger point: Files.com runs on top of your storage. The data stays in S3, and Files.com adds the parts S3 doesn’t have — sign-in through SSO instead of handing out bucket credentials, role-based permissions, audit, the protocols, automation, and the workflows real people use. With the remote-server mount, access that would otherwise need an IAM credential goes through a permission layer instead. If your team has been told to build the file transfer layer yourselves, we’re the buy option, already built.