Cloudfront configuration
Using Jamroom
DannyA:1. Will this be added at some point? Those files represent a lot of hits to the origin server
No - there's no plan at this time. It would add a significant amount of complexity for files that are cached by the browser. And with HTTP/2 coming online, moving your CSS/JS to a CDN is no longer a good idea.
Quote:2. When an item in s3 is pulled into cloudfront, it sits there and it may or not get refreshed based on the header info. If you update a file in JR, and clear your cache, you will need cloudfront to come and fetch the new file. You need to invalidate the object. You need to flush the file on cloudfront. I don't know what you want to call that. But how would you do that?
That's automatically done by CloudFront/S3 - when cloudfront sees a newer version of an object is in the source bucket, it gets updated.
Quote:
3.So when creating the distribution specifically:
Origin Domain Name- Same as bucket in s3 config
Origin Path-Blank
Restrict Bucket Access- NO (default)????
If you read the help for this in the AWS control panel it will tell you why you would (or would not) want to do this. This really isn't JR related.
Quote:Restrict Viewer Access(Use Signed URLs orSigned Cookies)- NO
Viewer Protocol Policy-HTTPS Only(if applicable)
Allowed HTTP Methods- GET,HEAD
Yep - pretty much everything at the default is good.
let me know if that helps.