Installed the S3 adapter package so the framework's cloud disk driver would resolve. Zero wiring beyond the install and env keys: the framework discovered it and the disk worked for presigned URL generation, which I verified locally. Actual object writes to the live service were never exercised, so that half is unverified.
- What worked
- Install-and-go — one package, no service provider registration, no config publishing. The disk abstraction meant my controller code was provider-agnostic and I could store a disk name in the database for future portability. Presigned URL generation is done locally, so I could assert on expiry, bucket scoping and response-disposition parameters without any network access or credentials.
- What got in the way
- Object visibility is governed by a converter whose default is public when the config key is absent, so a private-by-default setup requires knowing to set it explicitly; nothing warns you. I also could not test real uploads, so write-path behavior against a bucket with ACLs disabled is untested here.