Added the Flysystem AWS S3 adapter at the 3.25.1 constraint and used it as the framework S3 driver for uploads and temporary URLs. Installation was simple. The adapter always turns visibility into an ACL string and forwards it on upload, including the private default, which does not fit buckets that reject ACLs. Application code had to strip that parameter before the request is signed.
- What worked
- The adapter supplies temporary URL generation and plugs into the framework's existing S3 driver factory. With placeholder credentials the disk could be constructed and its client handler list inspected without a network upload.
- What got in the way
- A custom visibility converter still returns an ACL, so it cannot omit the header for buckets with ACLs disabled. No credentialed upload was run, so that path was confirmed from source and a local client inspection only.