Our S3-compatible endpoint allows any S3 client or SDK to connect directly to Files.com and perform uploads, downloads, and object management operations. This capability makes Files.com accessible from the broad ecosystem of tools, automations, and applications that already speak the S3 protocol. Instead of building custom integrations or relying solely on our REST API, customers can use familiar S3 commands and libraries to interact with their Files.com environment.

Benefits for Your Environment

Many organizations have internal systems and vendor tools that are already wired to send or receive data using S3. Until now, using those systems with Files.com required custom scripting or a protocol change. The S3-compatible endpoint removes this friction by presenting your Files.com site as an S3 bucket, making it easier to integrate Files.com into existing workflows without rewriting code or replacing tooling.

The S3 protocol is also a common denominator across cloud platforms. By supporting it natively, Files.com fits more naturally into multi-cloud and hybrid environments where data may originate from multiple systems but ultimately needs to be centralized, shared, or automated through a controlled platform.

Use Cases

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

A software vendor may require 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 allows the artifacts to be stored, audited, and distributed without modifying the vendor tooling.

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

Access to the S3-compatible endpoint works alongside other Files.com features such as Automations, Remote Mounts, Folder Settings, and Sync.

How to Use the S3-Compatible Endpoint

Our S3-compatible endpoint can be used with S3 clients such as Amazon S3 CLI or Amazon S3 SDK.

Using this service begins by generating the access credentials you want S3 clients to use. Each S3 client can be configured 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.

This compatibility gives customers a straightforward way to integrate Files.com into systems designed around S3, while still benefiting from Files.com features like permissions, logging, link sharing, automations, and Sync workflows.

Getting Started

To begin using your S3-compatible endpoint:

1. Generate an S3 compatible API Key, which will include the required Access Key ID and Secret Access Key.
2. Configure your S3 client or SDK.
3. 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 can 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. This allows higher concurrency, predictable performance, and broad compatibility with cloud-native tooling.