• http://www.wordimpressed.com Devin Walker

    I think there’s a large part missing in this section where you have to create an S3 Bucket Policy to make you files viewable by the public. Took me awhile to figure this part out…

    • jeffreifman

      Sorry about that Devin. I’ve seen different default behaviors – none of the other W3TC Cloudfront tutorials I’ve seen mention this either.

      • jeffreifman

        p.s. I’ve added a note at the end of this page.

  • http://www.facebook.com/mca.program Mca Programm

    I find it really usefully to me!

  • bakura

    Please note it’s not really recommended to use the access keys from the root account (as it has access to all services and can do everything, including launching new instances or removing existing one).

    You’d much better create a new IAM user with limited responsability (basically, only read/write access to AWS Cloudfront), and give this key. This also allows that if someone find your root AWS key and that you are using in all your applications… good luck ! IF someone find the key of your AWS Cloudfront access, just remove it and change it, without impacting all the other applications.

    • http://jeffreifman.com/ Jeff Reifman

      Excellent point, thanks Bakura.

  • pricenext

    Hi – I am using cloudfront along with CNAME & w3 total cache and everything is working fine -

    mydomain.com (Main Site)

    cdn.mydomain.com (CloudFront)

    Both the versions are fully functional. Since it might create duplicate content issue on google search i just want to load image/js files from the cdn.mydomain.com and not the entire site from cdn.mydomain.com.

    Is there a way to handle this? Temporarily i have used rel=canonical which will prevent duplicate issue.

    Please let me know