Menu

Tenant-Isolated AI Image Storage: Cheap Signed Downloads, No Open Bucket
📰

Tenant-Isolated AI Image Storage: Cheap Signed Downloads, No Open Bucket

DEV Community: go·YannickSterling6563·8 days ago
#MFRliZoc
#devtogo#devto#dev#storage#tenant
Reading 0:00
15s threshold

Short answer: For a logistics AI app, keep generated images in private object storage, authorize the tenant in the application, and issue a short-lived signed download link so the app does not proxy the media bytes.

Keep it private.

That answer is intentionally boring. Boring is useful when a fleet operator uploads a 300 MB inspection video, an image model produces several derivatives, and two customers happen to use the same filename. The storage bill matters, but tenant isolation matters first: a low-cost design that can cross an account boundary is not a low-cost design.

I learned to treat this as a delivery contract, not a bucket setting. The application owns identity and authorization; storage owns the bytes; the signed link is a temporary handoff. The invariant is that a tenant must never be able to choose an object key and thereby choose another tenant's object.

The tenant contract comes before the bucket

Consider a bounded production scenario.…

Continue reading — create a free account

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