AI-generated images belong in private, tenant-scoped object keys, not in a temporary buffer or a public bucket. In Node.js, stream the image response into an S3-compatible PutObject request, set metadata before the write, and make the key deterministic enough to prevent accidental replacement. For a gaming SaaS, that gives each studio a reproducible training-artifact path while keeping the operating bill understandable.
TL;DR
Use the AWS SDK's Upload helper with the readable body from fetch . Keep ACL private, put the tenant and training job in the key, and check the key with HeadObject before writing. Treat retention as an explicit policy. A storage service with a common REST contract can reduce integration work, but it cannot remove the need for tenant boundaries, lifecycle checks, or recovery decisions.
The constraint that changed my choice is tenant isolation. A solo SaaS can afford a few extra lines of validation; it cannot afford a training image from Studio A being addressed through Studio B's key.…