TL;DR
Private object storage plus short-lived signed download URLs is usually the cleanest delivery pattern for AI-generated images: keep the bucket private, authorize an application image ID before signing, and choose a service only after modeling retained bytes, requests, delivery traffic, and operational work. A public bucket is not required.
The important decision is not which storage price looks smallest in a comparison table. It is whether the complete image path protects tenant data and stays predictable after a notebook becomes a product. Generated images often begin as disposable outputs, then turn into feed cards, support attachments, exports, and evidence in an evaluation run. Their storage shape changes before anyone updates the original estimate.
How should an AI app deliver private generated images with signed download links?
Use two identities, not one. The database-facing identity is an application image ID, owned by a user or tenant.…