The Files.com S3-compatible endpoint enforces strong authentication, encryption, and permissions. This page explains how the service protects your data and how you can manage access securely.

Encryption

Connections to the S3-compatible endpoint always use HTTPS with modern TLS. Files.com encrypts objects at rest using secure server-side encryption. You do not need to configure encryption manually unless your workflow requires additional metadata for client-side encryption.

Authentication and Authorization

S3-compatible operations authenticate using Access Key ID and Secret Access Key pairs. Each Access Key ties to a Files.com API Key, inheriting the key's permissions and folder visibility.

You can revoke or rotate keys at any time. Revoking a key immediately invalidates all current and future requests signed with that key.

Permissions and Access Boundaries

Files.com applies the same role-based and folder-level permissions to S3 operations that it applies to other protocols. Users only see objects they are authorized to access.

Partner users, user permission fences, and root-folder restrictions all apply to S3 traffic as expected.

Network Access and Endpoint Control

If your organization restricts traffic through firewalls, allow outbound HTTPS access to the Files.com S3-compatible endpoint. Because Files.com uses regional architecture and DNS-based routing, allow connections based on DNS name rather than static IP addresses.

Monitoring logs in your Files.com site provide full visibility into S3-compatible access, including authentication attempts, object operations, and administrative changes.