Private Document Signed URLs: How S3, R2, Supabase and Firebase Storage Compare
A customer's inability to download a signed contract, and a spike in expired-link responses, illustrates the problem this comparison addresses. The article recommends issuing short-lived presigned URLs only after an application-level ownership check. It advises choosing among S3, R2, Supabase Storage, and Firebase Storage by benchmarking throughput, link lifetime, and egress costs on identical test fixtures. Suggested pass criteria include a completed download with a valid signature, zero unauthorized reads, and a p95 throughput meeting the contract workflow's needs. The author also recommends logging request metadata while never recording raw signed URLs.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in