Node.js Backup Restore Flows: Signed URLs and Tenant-Isolated Private Storage
The article recommends keeping backup objects private and verifying them with a HEAD request before offering any restore action. It advises issuing short-lived, single-object signed URLs only from admin-only backend routes, with tenant identity enforced in the authorization check rather than relying on bucket policy alone. It notes that signed URLs are a delivery mechanism rather than an authorization system, and that overwrite protection must be coordinated at the application level since some storage providers lack conditional writes. The piece compares several storage options, including Amazon S3, Cloudflare R2, Google Cloud Storage, and Infrai, highlighting Infrai's plain REST API and its lack of object versioning or conditional writes.
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