Menu

Node.js Presigned URL Audit for Backup Downloads (Object Storage Retention)
📰

Node.js Presigned URL Audit for Backup Downloads (Object Storage Retention)

DEV Community: go·Haelion14·14 days ago
#3ZhqBv4O
#devtogo#devto#dev#snapshot#restore
Long article (1466 words) — no AI summary yet.
Reading 0:00
15s threshold

A selected backup snapshot should remain private until an authorized tenant asks to restore it. The least complex way to deliver its archive is a short-lived presigned download URL for one object, issued after a tenant-scoped lookup. The deletion timer belongs to the snapshot record, not to the link.

TL;DR: treat a presigned URL as a bearer credential, not delivery proof. Keep the backup object private, authorize the snapshot before signing, record issuance without recording the URL, and alert only when a restore is stalled past evidence you can trust.

For an e-commerce system, this matters after the order database or a tenant configuration has to be rolled back to one selected snapshot. A predictable object key is convenient during an incident. It is also the wrong authorization boundary. The download service needs to resolve an opaque snapshot ID, verify that it belongs to the requesting tenant, and then sign exactly that stored object.

The two clocks are easy to conflate.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.