For -s (--ssl) You used to be able to use just one certificate (with SSL_CERT_FILE) to identify all the s3.amazonaws.com, but recently AWS has started using more than one CA. So oops, syncs will start failing....
There is a debian package ca-certificates; this is what I'm using now. apt-get install ca-certificates and then use: SSL_CERT_DIR=/etc/ssl/certs
But what if you don't know how to get certs for your platform in a format that ruby can digest? Well first I recommend seeing if your vendor has a "correct" way to get a trusted CA list set up.
In case it's helpful, I synced my "/etc/ssl/certs" dir to ServEdge_pub:s3sync/certs So you can pull my copy of the certs dir down if you want. It turns out all the cert files are just symlinks to the ca-certificates.crt file. So you could just use s3cmd to get ServEdge_pub:s3sync/certs/ca-certificates.crt, and then use the SSL_CERT_FILE setting to point ruby at that. That's how I do it in Windows, because the symlinks don't translate cross platform anyway.
Hi all. I wanted to put this note into announcements for anyone who is watching this board, because there has been an AWS change that can break your s3sync setup.
Already loads of threads talking about s3fox incompat with s3sync, and about the fiction of "directories" on s3. I have mixed luck with fox. Sometimes it shows a "dir" as a file, but if you add that to the path manually it will go "in" to the "dir" that it didn't think was there.
There is not really anything in your question I can use to diagnose what is going on. Could be anything. Path problem? File format problem? Permission to file?