Cloudfront configuration
Using Jamroom
No. As in my original post. It is not pulling from cloudfront. All the objects are coming from s3. All the media has s3 hostname.
Forum Activity for @dannya
Cloudfront configuration
Using Jamroom
Yes, that is working correctly, but nothing is pulling on the site.
updated by @dannya: 12/08/15 01:55:47PM
Cloudfront configuration
Using Jamroom
I'm not sure where I get the cloudfront url. Does it just replace the hostname of the s3 bucket or the whole s3 path?
e.g.
S3 butcket
https://s3.amazonaws.com/bucketname/media/imagename.jpg
Cloudfront domain name shows xxxyyyzzz.cloudfront.net
So is cloudfront URL?
https://xxxyyyzzz.cloudfront.net/bucketname/media/imagename.jpg?
That is not working, but I suspect it's incorrect
Cloudfront configuration
Using Jamroom
OK. I configured everything with the defaults. The distribution is enabled and I uploaded the key to JR. However nothing is coming through cloudfront
Cloudfront configuration
Using Jamroom
1. Will this be added at some point? Those files represent a lot of hits to the origin server
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?
3.So when creating the distribution specifically:
Origin Domain Name- Same as bucket in s3 config
Origin Path-Blank
Restrict Bucket Access- NO (default)????
Restrict Viewer Access(Use Signed URLs orSigned Cookies)- NO
Viewer Protocol Policy-HTTPS Only(if applicable)
Allowed HTTP Methods- GET,HEAD
Cloudfront configuration
Using Jamroom
1. I assume this only caches media items in the s3 bucket. It will not cache .js, .css, or other static content.
2. How does this deal with cach clearing? When you clear the cache on JR, does it also clear it on CF?
3. The module config was pretty straightforward. As far as I can tell, just create a key and add it to the module configuration. However, do you also need to set up a cloudfront distribution? If so, can you provide some guidance on the minimum configuration to get that working? Especially with regards to the url signing settings.
updated by @dannya: 03/24/16 08:34:33AM
Replacing image uploader
Jamroom Developers
It's fine. We will have to create our own blog or branch the existing one. Unfortunately, we needed something that allowed users to crop and resize images. There were too many users that were uploading images that were the wrong size or aspect ratio. Users are getting used to most modern sites giving them the ability to edit their photo in place. We needed to implement something. You might want to consider updating it at the core level.
