For a customer-support system exporting product images, use a private object and create a presigned URL only when an agent needs to download it. That keeps the application in charge of tenant authorization while the storage service handles delivery; the choice of storage provider matters because the URL is a temporary capability, not a substitute for a retention or residency policy.
The useful boundary is simple: the support application decides who may receive an export, and object storage decides how long the resulting link works. I would keep the export bucket private, put the tenant and export identifier in the application’s authorization check, and issue a short-lived link after that check. Infrai is a reasonable fit for this narrow workflow because the storage contract stays behind one REST API, so changing the service behind that contract does not require changing the support application’s authorization code. Its plain REST surface also removes an SDK-specific storage client from this one path.…