Implementing Amazon S3 for WordPress Blogs

amazon s3 wordpress

Note: Since writing this, we’ve since migrated to Flywheel with a Content Delivery Network powered By StackPath CDN, a much faster CDN than Amazon.378

Unless you are on a premium, enterprise hosting platform, it’s difficult to get enterprise performance with a CMS like WordPress. Load sharing, backups, redundancy, replication, and content delivery don’t come cheap.

Many IT representatives view platforms like WordPress and use them because they’re free. Free is relative, though. Put WordPress on a typical hosting infrastructure and a couple hundred simultaneous users can bring your site to a grinding halt. To assist in my blog’s performance, this week I modified my installation of WordPress push all of the graphics from Amazon S3 (Amazon Simple Storage Service). This leaves my server to simply push HTML via PHP/MySQL.

Amazon S3 provides a simple web services interface that can be used to store and retrieve any amount of data, at any time, from anywhere on the web. It gives any developer access to the same highly scalable, reliable, fast, inexpensive data storage infrastructure that Amazon uses to run its own global network of web sites. The service aims to maximize benefits of scale and to pass those benefits on to developers.

To convert the site for Amazon S3 took a bit of work, but here are the basics:

  1. Sign up for Amazon Web Services.
  2. Load the Firefox Add-on for S3. This provides you a great interface for managing content in S3.
  3. Add a bucket, in this case I added
  4. Add a CNAME to your Domain Registrar to point a subdomain from your site to Amazon S3 for virtual hosting.
  5. Download and install the WordPress plugin for Amazon S3.
  6. Set your AWS Access Key ID and Secret Key and click update.
  7. Select the subdomain/bucket you created above for the Use this bucket setting.


The next steps were the fun part! I didn’t want to just serve future content from S3, I wanted to serve all content, including ads, themes, and past media files.

  1. I created folders for ads, themes, and uploads in my bucket on S3.
  2. I backed up all my current content (image and media files) to the applicable folders.
  3. I modified my CSS file in my theme to pull all images from
  4. I did a MySQL search and replace and updated every reference to media content to be displayed from the S3 subdomain.
  5. I updated all image references for ads to be displayed from the ads folder on the S3 subdomain.

From here on out, I simply need to upload media to S3 rather than using the default image upload dialogue for WordPress. The plugin does a fantastic job in putting an S3 icon in the same location of Upload/Insert icons in the WordPress admin.

Moving all of the data and running on S3 for a couple days now has resulted in $0.12 in S3 charges, so I’m not concerned about the fees involved – perhaps a few dollars a month is what it will cost. On the plus side, if I get a ton of visitors, I should be able to handle many more than the current platform handles. My site is loading the home page in about 40% of the time that it used to, so I’m quite happy with the move!

The nicest thing about this move is that it didn’t actually require any development!


  1. 1


    I have an Amazon S3 account, but after trying to figure things out, I just left it because it is too difficult. Does the firefox addin for S3 make it a lot easier?

  2. 3

    I should add, you will need to point your CNAME to the new instead of to But after that, you treat it just like a normal S3 bucket.

    It does cost more when using the higher speed/low latency CloudFront option. If you decide you’d rather switch back to the standard S3 version, just switch your CNAME to point back to instead.

    About a year ago, I wrote <a href=""a few blog posts on Amaon S3 for anyone interested.

  3. 4

    If you're looking for even more of a speed increase, turn your Amazon S3 Bucket into a Amazon CloudFront bucket, which creates a true global multi-server, low latency Content Distribution Network. Here a link with all the details:

    Also, the wp-supercache plugin can give tremendous speed increases on high-traffic sites as it greatly reduces CPU load and database calls.

    • 5

      Very cool, Carlton! So it's very much a distributed network such as Akamai. I didn't realize they had that available! I may take advantage after seeing some of the costs.

      I have had caching with wp enabled before, but I have some dynamic content so I really struggled with it since it would sometimes cache content that I actually wanted to load real-time.

      • 6


        From their description it sound's like Amazon is doing something completely different, they say:

        “Amazon CloudFront uses 14 edge locations in major markets worldwide. Eight are in the United States (Ashburn, VA; Dallas/Fort Worth, TX; Los Angeles, CA; Miami, FL; Newark, NJ; Palo Alto, CA; Seattle, WA; St. Louis, MO). Four are in Europe (Amsterdam; Dublin; Frankfurt; London). Two are in Asia (Hong Kong, Tokyo).”

        Their basically taking advantage of internet exchanges to leverage their closeness to the end user where as CDN's like Akamai have servers much closer to the end user usually within the ISP's network.

        Amazons way of doing it is a lot cheaper and more effective Akamai.

        Rogerio –

  4. 7

    I wouldn't say it?s difficult to “get enterprise performance with a CMS like WordPress.”

    It's all in how you setup your infrastructure or the way you host your CMS.
    The way the CMS itself has been coded can also play a big part in its performance as Carlton pointed out with using the wp-supercache plugin.

    It would have been better if the functionality of the wp-supercache plugin was built in to wordpress from the start – but that would require re writing the front end. Which is what did.

    Off loading static content to something like S3 is a good way to offload processing and delivery from the main server. It?s an easy and convenient way of tapping into Amazons infrastructure to do the heavy lifting but once you reach a cretin threshold, Amazon will start to get expensive and it will be cheaper to do it in house and go with a CDN.

    Rogerio –

    I've been thinking about that situation for a bit, if just 100 people got together and contributed each month the price of a decent server that they would normally be paying for they could build/put together hosting infrastructure that could handle almost anything.

  5. 8

    $0.12 for the first couple days of S3 services. Would you revisit the topic in a few months and show some stats of traffic versus costs? It'd be interesting to see how the cost breaks-down to unique visitors and against ad costs or other inputs.

  6. 13
  7. 14

    Amazon S3 is an incredibly well valued service. I'm just in the process of integrating it into a CMS. The only issue that I've come across from a development perspective, not an Amazon service perspective, is that if you want your user to transparently upload the file directly to S3 via POST and you have a multipart form that incorporates text destined for your local database, you're stuck. You either need to separate it into two forms, or try use ajax to upload the file first then on success submit the data locally.

    If anyone has a better solution, feel free to let me know :o)

    Nonetheless, the cost savings for hosting large high traffic files warrants the development of such a system.


    Suppression List Management Systems

  8. 15


    Great write up. I have stepped through as you describe, but in my admin panel where I upload images, I dont see an S3 button. I have noticed that my images, when uploaded normally end up on Amazon, does this mean I can now copy all my existing images over and delete the ones on the server?

    And do I need to modify where my images come from or does the plugin do this?

  9. 16

    Hi Scott,

    You should see a little database looking icon to the right of your typical icon. That’s the icon to pop up the Amazon window. I moved all of wp-content/uploads to Amazon and made sure I had the same path… the only difference being the subdomain. They were at http://www... and now they’re at After I copied all the images over to Amazon, I used PHPMyAdmin and did a search and replace for src=” and replaced it with src=” (

    Hope that helps! It’s not seamless, but it works.


  10. 17

    Hey Douglas, thanks for that, I have updated the DB so all images point to images., but I see some of the thumbs (when looked at via the page info) shows the iamge still at www.

    Here is the site ( – a, alos having some major memory issue for the front page, only started once we shifted hosting, hence me now looking at offloading some of the hosting pressure to S3. 😎

  11. 18

    do you know if it is possible to just upload to S3 without it also storing a copy on the local server?


  12. 19
  13. 20
    • 21

      It is compatible with the latest version, but I honestly don’t like the way it works – you have to shift and load all images to S3 with a different process. We may actually build a more robust CDN (Content Delivery Network) integration with WP that synchronizes rather than demands a different process.

  14. 22
  15. 23

    Do you know if this works with “External Buckets” too? I want to set this up for a blog of a friend of mine and let him use a bucket in my AWS account (I already created a user account for him and gave him access to one of my buckets using the Amazon IAM tools).

  16. 24
  17. 25
    • 26

      Celia, go to the AWS home and under the “My Account / Console” drop down, select “Security Credentials.” Sign in if you need to. From there, scroll down to Access Credentials and you will see your Access Key IDs listed. Copy one of those for the key ID for this plugin, and then click on the “Show” link to see the longer Secret Access Key. Copy that and paste it into the plugin settings as well. You should be all set after that!

  18. 27
  19. 28

What do you think?

This site uses Akismet to reduce spam. Learn how your comment data is processed.