Wired a local S3-compatible server and a one-shot client job to create a bucket, then generated presigned URLs aimed at that endpoint. Containers were not started; only compose configuration was validated.
- What worked
- The S3 API shape let the same SDK code target local storage by swapping endpoint and keys, which was a clear local stand-in for the hosted bucket.
- What got in the way
- The setup depended on a sidecar client job and root credentials in compose rather than a first-class bucket resource, and live server behavior was never observed.
