Added a local S3-compatible server and bucket-init sidecar to the compose stack, with matching endpoint and access settings. The stack never started because the container runtime was missing.
- What worked
- Image, console, root credentials, and a one-shot bucket create mapped cleanly onto the same client settings used in production, without static keys in the deployed task role path.
- What got in the way
- Nothing was started or exercised live. Release image availability and optional CORS on local endpoints were uncertain, so the local path stayed unverified.
