'%20transform='translate(102%20102)%20scale(.8)'/%3e%3c/svg%3e){kind=small}
Help center
What if an S3 tool fails authorization?
Use the S3 error code to check signatures, bucket permissions, CORS and request size.
Troubleshoot by error code
| Issue | Check in this order |
|---|---|
| SignatureDoesNotMatch | Check Region, path style and device time; keep the signed URL's host, path and query parameters unchanged |
| AccessDenied / 403 | Check key status, target bucket, read/write access and key policy; private files also require a valid signature |
| Automatic CORS setup failed | Inspect the PutBucketCors error. Read-only keys cannot write CORS rules; distinguish connectivity failures from permission denial |
| NoSuchBucket / NoSuchKey | Check the bucket identifier, folder hierarchy, filename case and actual upload location |
| EntityTooLarge / 413 | Check single PUT and part-size limits. Enable multipart upload for large files; the total object limit still applies |
| Request expired | Sync device time and generate a new URL. Use the tool-generated expiry; do not alter signature timestamps manually |
| TLS reset / 5xx | Check connectivity, certificates and origin status for the Endpoint and download domain separately; these errors do not necessarily indicate incorrect keys |