Posts from the Tigris engineering team about how we build global object storage for any cloud — low-latency access anywhere, millions of buckets, and 99.99% availability you can rely on.
SigV4 looks simple: sign a request, check the signature. Then you implement
canonicalization, clock skew, and a cache that isn't allowed to hold your key.
Presigned URLs are replay attacks you commit on purpose. How SigV4 signs the
clock, what a presigned URL grants on Tigris storage, and what it costs you.
Storage-protected Mastra agents: a reference implementation. Isolated session forks, validate before promoting, contain compromise at the storage layer.
Tigris is a globally available, S3 compatible object storage service. In the first post of the series we will share the details of how we have built the authentication and authorization support in Tigris.
Client-side encryption, a fortress of digital privacy, empowers users to safeguard their information with an impenetrable shield. By arming individuals with the cryptographic key to their data, this formidable approach ensures an unparalleled level of control, fortifying the sanctity of personal inf…