News for hackers. Stuff that matters.
Re:Google, Microsoft, Qualcomm and Baidu Announce Joint Inve... by LoSboccacc on Tuesday September 22, 2015 @12:05PM (#10259475)
we use it on our image heavy startup. reduces the load on the server by a fair margin, and since images are loaded on S3 it also reduces the operating cost quite a bit

additionally it's geolocated, so we get that for free, which is nice.

Re:Google, Microsoft, Qualcomm and Baidu Announce Joint Inve... by waffle_ss on Tuesday September 22, 2015 @12:23PM (#10259611)
How are you using CloudFlare for S3 images? Are you using Flexible SSL?

The problem I ran into was setting up a CNAME for an S3 bucket requires the bucket name to have periods in it, but https:// access no longer works for buckets with that naming convention[1]. So I ended up having to use CloudFront instead for my images.

[1]: https://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestri...

Re:Google, Microsoft, Qualcomm and Baidu Announce Joint Inve... by LoSboccacc on Tuesday September 22, 2015 @12:38PM (#10259722)
there is a middleware included :P

we have a document store backed by S3 running on EC2 instances, the instances are behind one of amazon balancing routers and that's what the cloudflare cname points at

currently the beta env runs flexible ssl and production runs with strict.

Re:Google, Microsoft, Qualcomm and Baidu Announce Joint Inve... by ehPReth on Tuesday September 22, 2015 @10:41PM (#10263057)
There's an alternate URL prefix you can use if your bucket name has periods: http://documents.scribd.com.s3.amazonaws.com/docs/91ltsqq5fk... becomes https://s3.amazonaws.com/documents.scribd.com/docs/91ltsqq5f...
Re:Google, Microsoft, Qualcomm and Baidu Announce Joint Inve... by waffle_ss on Thursday September 24, 2015 @01:26AM (#10269986)
If you use s3.amazonaws.com then you aren't using a CNAME anymore, meaning you can't use CloudFlare to accelerate the traffic. CloudFlare needs to control the DNS.