Make Amazon S3 A Managed File Transfer Platform

Yes. Files.com connects to any S3 bucket you hold credentials for, whether it's your own, a partner's, a vendor's, or a customer's, and can pull files from it or push files to it. The bucket does not have to live in your AWS account.

No. Files.com connects to an S3 bucket with credentials alone, so you can run on Google Cloud, Azure, or your own servers and still exchange files with a partner or vendor who standardized on S3. No AWS footprint of your own is required.

Files.com stores nothing outside your bucket unless you ask it to. Connect the bucket as a Remote Server Mount and Files.com passes every operation through to S3 in real time. Nothing is copied onto Files.com. You can also have Files.com hold a copy, as a backup, a faster-access tier, or because you want Files.com to be the primary store. To do that, use a Sync and choose the destination. Files.com has its own high-performance storage. Whether the data lives in S3, on Files.com, or both is your call, not a default.

Yes. Files.com supports AWS STS with IAM role assumption. The role uses temporary credentials that Files.com auto-renews. For most production environments, STS role assumption is the recommended path. It reduces credential exposure and follows AWS best practices for cross-account access.

Yes. When a bucket only accepts connections from inside your AWS network, you can run a small Files.com Agent in that network and it reaches the bucket from the inside. Nothing on the bucket has to be opened to the internet.

Yes. Files.com integrates with GovCloud buckets as a connection target, the same way it connects to any other customer cloud. Files.com itself does not host in GovCloud. Files.com is separately FedRAMP Certified at Class A under FedRAMP 20x, with Class B in progress.

Files.com supports the Standard, Standard-IA, One Zone-IA, Intelligent-Tiering, and Glacier Instant Retrieval storage classes. Glacier Flexible Retrieval and Glacier Deep Archive are not supported. Those tiers are designed for long-term archive where retrieval takes hours, and that does not work with the active-file-operation model that Remote Server Mounts and Syncs run on.

No. The S3 integration is included in every Files.com plan. The only AWS-side costs are S3 storage and any data transfer your workload generates.

Files.com Starter is $199 a month with every protocol included. AWS Transfer Family is $216 a month for SFTP alone, and each other protocol costs extra. Files.com comes ready to use on day one, with SFTP, partner setup, the activity log, automation, and a real screen people can use. Transfer Family gives you the connection part. The rest you build yourself out of AWS Lambda, Step Functions, and EventBridge.

Yes. Files.com works with IAM policies scoped to the specific bucket and object prefix your integration needs. Both full-access and read-only policies work, so you can grant least-privilege access to exactly the path the workflow touches.

Yes. A Files.com Automation can use a mounted S3 bucket as the place it pulls files from, the place it sends them, or both. Files.com treats a mounted bucket exactly like its own storage.

Files.com mounts the bucket where it is; the data stays in S3 and every protocol, automation, and permission works against it in place. When the job is a one-time move of the contents of the bucket to Azure Blob, Google Cloud Storage, Wasabi, or Backblaze B2, that is what Mover, the one-time migration tool from Files.com, is for: a free dry run counts the objects and prices the move, including the S3 egress, before anything leaves the bucket.