Using Amazon S3 to Host Images on Your Website/Blog

by Crystal

One of the foundations of a good website is that it loads fast. If your site loads slowly, people will click away and you’ll lose them! If you’re paying to drive traffic to your site, you’re throwing money out the window if your visitors aren’t staying long enough to buy from you.

By hosting your images on Amazon S3, you can drastically improve your site’s load time. Just switching your main media files to Amazon S3 will help most sites see improvement.

To get started with Amazon S3, visit Amazon Web Services, sign up for a free account, and watch the video below.

This video covers:

  • Creating a bucket
  • Creating a file folder
  • Uploading images
  • Setting permissions on images
  • Finding the image link
  • Putting the image on your WordPress blog

How to Create an E-Course
Turn Your Knowledge into Automated Income
See exactly how to create your own e-course with no program design skills
The best way to create a great e-book in a matter of hours
How to price your e-course in a way that will bring you the most income
Regular Price: $49
On Sale for $19*
*For a limited time only!

{ 4 comments… read them below or add one }

Hypejar October 21, 2012 at 6:34 pm

We recently implemented this in Hypejar. The load time is great, and images load way faster.

Reply

Crystal February 12, 2013 at 3:56 pm

Thanks for the recommendation, I may give it a try!

Reply

Allan February 12, 2013 at 12:04 am

Crystal.
Thanks for the very clear video tutorial. Can you tell us how to set Bucket permissions so that all of its content objects are safely publicly viewable by default? I’m confused if I’m to use List permission for Everyone, or if I shou;d create a policy to getObject…. etc.

Reply

Crystal February 12, 2013 at 3:56 pm

In my experience with S3, I never set bucket permissions, only file permissions (public- everyone). The only permission I’ve ever had to worry about is that one- so beyond that I can’t advise.

Reply

Leave a Comment

Previous post:

Next post: