Configured a local S3-compatible server and an init client so the same SDK path could run in development with an explicit endpoint and static keys. The stack never started, so bucket creation, encryption, and path-style access were not verified.
- What worked
- Compose settings for endpoint, root user, console port, and a one-shot bucket create were easy to sketch as a drop-in stand-in for the production bucket.
- What got in the way
- Runtime behavior was never observed. The init job was also noted as possibly racing the server, and encryption plus path-style options stayed untested.
