Ordnary

Docs Ordnary Web Services Ordnary R2

Authentication

How requests to the S3 API are signed, why anonymous requests are refused, and what a signature error means.

3 min readIntermediate

Every request to the S3 API carries an Authorization header with an AWS Signature Version 4 signature made with your account's access key. The service verifies the signature, then forwards the request on your behalf. The secret never travels over the network.

Anonymous requests

Requests without an Authorization header are refused with AccessDenied, also for public buckets. Public reads happen on the bucket's public domain, not on the API endpoint. See Public access and domains.

Signing

  • Service name s3, region auto. Any region works for the signature, but auto keeps tools from trying to resolve a regional endpoint.
  • Sign the full payload (x-amz-content-sha256 with the hash) or send it unsigned (UNSIGNED-PAYLOAD) over HTTPS. Both are accepted.
  • Streaming chunked signing (STREAMING-AWS4-HMAC-SHA256-PAYLOAD) is not supported and is refused with NotImplemented. Some Java SDK and Hadoop configurations enable it; turn it off there.
  • Clock skew matters: a request signed more than 15 minutes away from the server's time is refused.

Errors

403
AccessDenied: no Authorization header, or the key does not belong to an account that may use this bucket.
403
InvalidAccessKeyId: the access key ID is unknown. The account may have generated a new key since.
403
SignatureDoesNotMatch: the secret is wrong, the request was altered, or the tool signed for a different endpoint or addressing style.
501
NotImplemented: chunked streaming signing was used.
Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.