Object Storage API
S3-compatible object storage. Issue separate credentials per bucket, connect any S3 SDK directly, and pay nothing for egress on reads.
- Credentials: an Access Key / Secret Key issued per bucket and valid only for that bucket; the secret is shown once and a new key takes about a minute to activate
- SDK setup: region is always auto with virtual-host addressing; Node.js / Python / Go / PHP / aws-cli samples
- CORS: required before the browser can upload or read directly, and the origin must be a concrete domain, never a wildcard
- Presigned URLs: both uploads and downloads can be presigned, so you hand the browser a time-limited link instead of a key
- Limits and pricing: 5 GiB per single PUT and up to 10000 multipart parts; storage is billed on actual daily usage, and deletes and egress are free
Frequently Asked Questions
Why does a freshly issued credential keep returning 401?
A new credential takes about a minute to reach the storage nodes, and calls made in that window return 401 Unauthorized. It is not a wrong key — wait briefly and retry. This is the easiest thing to misdiagnose on a first integration.
What region should I use, and what causes SignatureDoesNotMatch?
Region is always auto. Using us-east-1 or similar breaks the signature and every request returns 403 SignatureDoesNotMatch. Also keep virtual-host addressing and do not enable path-style — that mistake shows up as 404 NoSuchBucket.
Related pages: Tovanix API Documentation · Cloud Service · Domain / Server / Email Routing All-in-One · Using cloud services (domains and servers)
Loading…