Table of Contents |
---|
CloudFront introduction
Amazon CloudFront is a web service that speeds up distribution of static and dynamic web content, such as .html, .css, .js, and image files, to end users by delivering relevant content through a worldwide network of data centers called edge locations that provide the lowest latency
...
- Magnolia Cloud user with granted permissions can access author instance for relevant applications
- Traditionally, user will work with assets stored in JCR via Assets app
- We also support Amazon S3 storage with S3 browser app. With this S3 app, user can create buckets, upload objects, and use them as normal assets
- Magnolia Cloud user will then work with CloudFront app to create distribution
- For assets stored in tranditional JCR, user will use the either the URL of author or public instance as the Origin domain name (public instance is recommended)
- For assets managed with S3, user will use the bucket URL as the Origin domain name (example: <bucket_name>.s3.amazonaws.com)
After CloudFront distribution has been created, a generated domain name will be returned (example: d22ze7mvgz7e1v.cloudfront.net). This is the domain name that will replace the normal domain name to take advantage of CDN support
For Magnolia Cloud user, the URL transformation will be handled transparently within the Magnolia API
Code Block language xml theme RDark <img src="${damfn.getAssetLinkWithCDN('s3:/myBucket/myFolder/my-asset.png')}" />
If user uploads a new version of assets, then this "magical" method will generate an updated link and everything else for invaliadating cache should work like a charm so there will be no user's intervention too!
- CloudFront also support custom domain if user don't want to go with the default generated domain when creating distribution
...
Page Turner | ||
---|---|---|
|