Just noticed that the short URL is not being recorded in the db. This doesn't cause issues when using the local store or S3 configs of the system since they are using calls directly to the filesystem to redirect pages. Relying on the db would probably notwork.
This broke right around the time of heartbleed and a shift in the use of secrets on AWS. The bottom line is that something changed in the API that now causes the very old S3 library being used to generate an error out of CURL - "SSL peer certificate or SSH remote key was not OK". I tried pointing CURL at a new set of root certs but it still won't work with S3. I suspect something that has to do with the way paths are handled on S3.
Anyway, no matter the cause, S3 storage is broken right now.