by greatamerican on 3/10/18, 7:12 AM with 38 comments
by subway on 3/10/18, 8:20 AM
A better way is to completely leave the "website" bits of S3 off, and leave that all up to CloudFront. You can create an Origin Access Identity, then grant that OAI access to read your S3 bucket (all automated in the wizard when you create a CF dist and specify an S3 origin). You then specify a default object in your CF dist, and bam, CF is using the S3 REST API over SSL to secure that CF-S3 hop.
by 3stripe on 3/10/18, 8:02 AM
by greatamerican on 3/10/18, 9:04 AM
by mike503 on 3/13/18, 6:23 AM
a) it's totally free, which means once it's cached at CF, no charges from AWS for bandwidth, also no charges for Route 53 since CF handles the DNS too.
b) it can be used to terminate SSL in front of the S3 bucket (with or without the S3 bucket properly using SSL, depending on if you're using path-based or host-based bucket access)
c) cache invalidations are stupid fast
d) any CDN changes are done nearly instant, vs. "however long" Cloudfront takes
$.02
by Mononokay on 3/10/18, 7:46 AM
by trevyn on 3/10/18, 2:54 PM
by navaati on 3/10/18, 11:41 AM
I'd rather have the site go down than me go broke, so is it really a good idea ?
by logronoide on 3/10/18, 8:22 AM
by praveenweb on 3/10/18, 1:37 PM
I think cloudflare gives more options as a CDN than cloudfront.
by edem on 3/10/18, 8:30 AM
by forty on 3/10/18, 1:07 PM
by IloveHN84 on 3/10/18, 12:05 PM
by greatamerican on 3/10/18, 8:09 AM