Short answer: for a logistics SaaS that serves private report images, keep image bytes and generated thumbnails in object storage, keep authorization and retention state in the database, and issue short-lived signed URLs only after an application-level permission check. The important design decision is the deletion record, not the storage brand.
That distinction matters for a customer who asks for a report to disappear. A database row can say “deleted” while an original, a 320-pixel preview, a worker's temporary output, and an old browser URL still exist elsewhere. I would define the retention boundary first, then choose the byte store that can fit it. The question is not only where the bytes live; it is which system can prove that each copy was found, revoked, and removed.
Deletion is a feature.
What does a retention-first image design need to guarantee?
Start with an inventory.…