Skip to main content

Troubleshooting the S3-Compatible Endpoint

When a request to the S3-Compatible Endpoint fails, Files.com returns an S3 error response to the client. Files.com also records each failed request signed with a valid Access Key ID in Inbound S3 Logs, where the Error Type and Error Message columns show the error Files.com returned to the client.

Signature Validation Failed

The error Signature validation failed, with an error type of SignatureDoesNotMatch, means the request failed authentication. S3 clients never send the Secret Access Key itself. Instead, the client uses it to calculate a signature for each request, and Files.com calculates the same signature using the Secret Access Key on record for that Access Key ID. When the two signatures do not match, the Secret Access Key configured in your client is not the one Files.com issued with that Access Key ID.

In Inbound S3 Logs, these entries record the Access Key ID and the requested path without an operation, because Files.com records the operation only for requests that pass authentication.

Configure your client with the exact Secret Access Key that Files.com displayed when you created the S3-compatible API key. Files.com displays that value only at creation time, so if you did not save it, delete the key and create a new one.

Request Fails and Does Not Appear in Inbound S3 Logs

The error Failed to validate credentials, with an error type of InvalidAccessKeyId, means the Access Key ID on the request does not exist on your site, because it contains a typo or because the key was deleted. A request that carries no S3 credentials at all receives the error Access denied, with an error type of AccessDenied.

Files.com cannot match these requests to your site, so no entry appears in Inbound S3 Logs. The logs record only requests signed with an Access Key ID that Files.com recognizes, including requests that fail.

Check the Access Key ID in your client against the values you saved when you created the S3-compatible API key. Files.com does not display the Access Key ID of an existing key, so if you cannot confirm the value, create a new key and configure your client with the new Access Key ID and Secret Access Key.

Cannot Download File

The error The specified key does not exist:, followed by the requested path, with an error type of NoSuchKey, means there is no file at that path.

List the parent folder from your client to confirm the exact path. A common cause is the bucket name, which is not part of your folder path. When a client's bucket setting contains one of your folder names, Files.com leaves that folder out of the path. When the file path begins with the bucket name, Files.com treats it as a folder name. Use the bucket name that matches your URL addressing style and keep it out of the file path.