The Files.com S3-compatible endpoint lets any S3 client or SDK connect directly to Files.com and perform uploads, downloads, and object management operations. Files.com becomes reachable from the ecosystem of tools, automations, and applications that already speak the S3 protocol. You can use familiar S3 commands and libraries to interact with your Files.com environment instead of building custom integrations or relying on the REST API.

Many organizations run internal systems and vendor tools that are already wired to send or receive data using S3. Pointing those systems at Files.com used to require custom scripting or a protocol change. The S3-compatible endpoint presents your Files.com site as an S3 bucket, so you can integrate Files.com into existing workflows without rewriting code or replacing tooling.

The S3 protocol is also a common denominator across cloud platforms. Supporting it natively means Files.com fits into multi-cloud and hybrid environments where data originates from multiple systems and needs to be centralized, shared, or automated through a single platform.

Use Cases

A manufacturing company has equipment that exports production reports using an S3 push mechanism. Pointing the equipment at the Files.com S3-compatible endpoint lands the reports directly in Files.com, where the data is shared with downstream teams or fed into an automated workflow.

A software vendor needs a location to deliver build artifacts created in their CI system. Most CI pipelines support S3 as an output target. Connecting that pipeline to Files.com stores, audits, and distributes the artifacts without modifying the vendor tooling.

A media organization uses a cloud rendering platform that only supports S3 for job ingest and asset retrieval. Using Files.com as the S3 endpoint lets the organization manage permissions, retention policies, and transfers while keeping workflow tools unchanged.

The S3-compatible endpoint works alongside other Files.com features, including Automations, Remote Mounts, Folder Settings, and Sync.

How to Use the S3-Compatible Endpoint

The Files.com S3-compatible endpoint works with S3 clients such as the Amazon S3 CLI and Amazon S3 SDK.

Start by generating the access credentials you want S3 clients to use. Configure each S3 client with the endpoint URL, access key, secret key, and chosen authentication method. The folder structure in Files.com maps directly to the paths requested by the S3 client, so existing scripts and tools can issue familiar commands such as PUT, GET, or LIST without modification.

S3 integrations on Files.com also use the platform's permissions, logging, link sharing, automations, and Sync workflows.

Getting Started

To begin using your S3-compatible endpoint:

Generate an S3 compatible API Key, which includes the required Access Key ID and Secret Access Key.
Configure your S3 client or SDK.
Upload or retrieve objects using standard S3 methods.

S3-Compatible Endpoint Details

Files.com operates a proprietary S3-compatible endpoint that we build and maintain in-house using our full-time employees.

The service operates on port 443 (HTTPS).

Automation and Workflow Integration

You can integrate S3 operations into CI/CD pipelines, backup systems, cloud workflows, and application services. Objects uploaded via S3 trigger Files.com Automations, appear in Syncs and Mounts, and participate in lifecycle rules.

You can extend workflows using Files.com Webhooks to coordinate downstream activities after object creation or updates.

Differences From Other Protocols

The S3-compatible endpoint uses an object storage model rather than a traditional hierarchical filesystem. Folders are simulated through object key prefixes. S3 clients treat each uploaded file as a distinct object without the concept of partial writes or local locking.

Compared to SFTP, FTP/FTPS, and WebDAV, S3-compatible operations rely on HTTPS REST requests and do not require persistent protocol sessions or channel negotiation. The result is higher concurrency, predictable performance, and broad compatibility with cloud-native tooling.