The S3 Compatible Remote Server connects storage services and private systems that implement the S3 protocol, including IBM Cloud, Oracle Cloud, and MinIO. It lets those systems participate in Files.com workflows without requiring every user or application to hold their storage credentials.

Use the native integration when Files.com lists the provider separately, including Amazon S3, Wasabi, and Backblaze B2. Those connection types supply the provider-specific settings. Use this generic connector when the service needs its own endpoint and S3-compatible connection details.

A Mount provides access to the remote files through a Files.com folder. A Sync transfers files between the bucket and another location.

Endpoint, Bucket, and Credentials

Select S3 Compatible when adding a Remote Server and provide an identifiable internal name.

Setting	Meaning
Endpoint	The service URL that Files.com will connect to. Its reachability must match the connection's selected network route.
Bucket name	The bucket within that service. Use the provider's bucket naming rules.
Region	The region value required by the provider. This setting is optional; leave it blank when the service supplies no region requirement.
Access Key and Secret Key	Credentials issued by that provider for the intended bucket and operations.

Enter credentials directly or select them from the Remote Server Credential Manager. Key creation and supported permissions depend on the service. The connection needs sufficient access to list and perform its intended file operations; the provider's S3 compatibility does not make its permission model identical to Amazon's.

For network restrictions, use the source addresses for the selected connection route. Private storage can be reached through Agent routing from a network that can reach its endpoint.

URL Addressing Style

Path-style addressing places the bucket after the hostname, as in https://s3.example.com/my-bucket/path/to/file. Virtual-hosted-style addressing places it before the hostname, as in https://my-bucket.s3.example.com/path/to/file.

Files.com defaults to path-style addressing. Select Use Virtual-Hosted-Style URLs when the provider requires the other form. The endpoint, bucket name, DNS, and certificate must support the addressing style you choose.

Transfers and Compatibility

Eligible client uploads and downloads use Direct Routing automatically. This avoids relaying those contents through Files.com and counting them as Files.com Transfer Usage. Web uploads use Files.com's network. Direct uploads also depend on the endpoint format: an endpoint containing a path prefix uses the relayed upload path.

Files.com does not expose a maximum-connection setting for S3 Compatible Remote Servers. These services handle parallel HTTP requests rather than FTP or SFTP sessions. If the destination cannot sustain the connection load, contact us to discuss the integration's requirements.

Large uploads can use multipart transfers. Incomplete uploads can leave parts stored at the provider, consuming storage and potentially incurring charges. Configure the provider's multipart cleanup or lifecycle feature according to its own documentation.

Object Storage Behavior explains implicit folders, zero-byte folder markers, and copy-and-delete moves. Folder representation, case sensitivity, versioning, and recovery ultimately depend on the connected service; do not assume every S3-compatible provider supplies every Amazon S3 capability.