82 Comments



  1. Hi,
    Thanks for specifying Bucket Explorer tool in your very good article to help users of Amazon S3 a lot.
    I am one of the developer team member, and we always well come the users feedback.
    Bucket Explorer provides an easy and complete GUI to implement all the functionality of Amazon S3, Cloud Front,SNS and Import-Export service.
    Use can perform Multipart-Upload and resume it,Multipart-Download, host your Bucket as S3 website and many more..
    http://www.bucketexplorer.com/

  2. Thanks dude, that’s exactly the info I was looking for!
    It worked great

  3. OK having problems getting this to work right.

    Trying to get assets.everythingfurniture.com to point to my bucket “everythingfurniture” and path to buckets under that as well.

    Is it possible? I did the cname thing and it keeps saying no such bucket exists. So I tried setting cname to everythingfurniture.everythingfurniture.com to point to s3.amazonaws.com since that is my bucket trying to access

    still get message saying
    NoSuchBucket
    The specified bucket does not exist
    everythingfurniture.everythingfurniture.com
    DA7B459FDFDD58D1

    assets.everythingfurniture.com also points to amazon and I get this message…

    NoSuchBucket
    The specified bucket does not exist
    assets.everythingfurniture.com

    Any suggestions?

  4. @Scott

    You need to find out what your full asset address is first.

    Example..

    everythingfurniture.s3.amazonaws.com

    The bucket tool will give you the fool address, also bare in mind, the UK and US versions are different.

    * Name: assets
    * Type: CNAME
    * Value: s3.amazonaws.com.
    * (If you are an European users, use s3-external-3.amazonaws.com. instead)

    Thats it!

    http://assets.everythingfurniture.com/


  5. Hi,

    I’ve found that the index.html wasn’t displaying, instead XML was rendered to the screen. So I changed my CNAME mapping to this instead:

    cdn CNAME cdn.mattauckland.co.uk.s3-website-eu-west-1.amazonaws.com.

    This is where the subdomain and bucket is cdn.mattauckland.co.uk.

    I don’t use CloudFront at the moment, as I want to skip the additional cost until I know what I’m paying each month. As you guest I’m new to S3, and this will be a trial as I’m looking to spread the load between S3 and my dedicated server.

    After making the CNAME change, the index page seems to work just fine.


  6. Hi, got a question. Has anyone here used AWS CloudFront. I’m thinking of hooking my bucket into CloudFront, but don’t know if I need to change my DNS record to the CloudFront entry or leave it as it is.

    1. In an update to my question, I now use CloudFront on my site for serving static content. Along with Route 53 it greatly speeds up my sites load time. A live example is http://djbook.co where content is served on a combination of S3 bucket, CloudFront (for static images like logos and such, plus CSS files), and Route 53 for DNS.



  7. Thank you just what I needed to know. Appreciate the detailed instructions.

  8. How can I fix a cname using a load balancer?, whats the easier way to configure a subdomain, using a load balancer or a s3 bucket?

  9. This was a great explanation, thank you, but you made a mistake. I was going to show this example to a customer, but he won’t understand now because, you refer to your domain as s3.carltonbale.com, yet your example (5.1) says subdomain.domain.com. (It should have said subdomain.carltonbale.com.)

    Thanks anyway. I’ll search for another example somewhere else. Sincerely yours..

  10. Hi This is a very useful article. You’re discussing about 3 urls:
    1 .subdomain.domain.com (as long as the bucket name is the same as the full subdomain name, it is not necessary to specify the bucket name again at the end of the url)
    2. your_bucket_name.s3.amazonaws.com
    3. s3.amazonaws.com/your_bucket_name

    Is there a way to restrict direct access by the world to 2 and 3 urls?

    Thank you.

  11. Great! I was having the same problem as Scott up there in the comments.
    My mistake was to create the bucket with the name “mybucket”.
    The correct way is to create the bucket with the name “mybucket.mydomain.com”.

    And then, create the cname as:
    mybucket -> s3.amazonaws.com

    1. I’ve also introduced AWS Cloudfront as a CDN to cache my static content on the website, content like images used in the design that don’t change that often.

      Made a big difference to website load times.

      I also used AWS S3 bucket for a Listen Again web app I built for a local radio station. Each radio show automatically recorded is now uploaded to S3, and then Cloudfront handles the CDN from there. Saves on storage costs, and makes the play back/download of MP3’s that much quicker.

      1. Author

        I’m now using AWS Cloudfront as well for a Content Distribution Network. The content gets auto-populated from web server using origin push from the WordPress caching plugin WP Super Cache. So users interact with WordPress as they normally would to upload pictures and files, and all static content is auto-populated to AWS CloudFront CDN. Super simple.

  12. Thank you for your helpful post. how does this affect the https certificate from the original site? Does the certificate cover the images hosted on S3 funneled through the subdomain? https seems to be the direction we need to go to have respect for our site. I had it working but the images off site threw up an unsafe warning. Better to not have encryption than to have that warning flash up to users. Any thoughts?

    1. No, your certificate doesn’t carry over to S3.

      Because I also serve my site as https completely (podbox.me), including static files like js and images, as well as audio files, I now use CloudFront CDN to distribute my S3 content.

      CloudFront supports secure and non-secure connections, which solves that problem for me. Now my whole site is secure, and fast.

      I hope that helps.

Leave a Reply to Carlton Bale Cancel reply