undefined | Better HN

0 pointswaffle_ss10y ago0 comments

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...

0 comments

3 comments · 2 top-level

ehPReth10y ago· 1 in thread

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...

waffle_ssOP10y ago

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.

LoSboccacc10y ago

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.

j / k navigate · click thread line to collapse