can't publish in a way that's HTTPS

[jeremybmerrill]

Driveshaft can't publish in a way that the output JSON file is accessible over HTTPS.

https://int.nyt.com/ doesn't work because the cert is for s3.amazonaws.com.

https://int.nyt.com.s3.amazonaws.com/ doesn't work because wildcard certs only match one level of dots down.

The solution, I think, is to make Driveshaft publish to a bucket with no dots in the name. I think @buth is creating one, called newsdev-secure-internal or something or like.

[buth]

This should be set outside of providing IAM permissions for Driveshaft to write to that bucket.

Ideally, we'd only give Driveshaft access to a subdirectory (/driveshaft).