S3 for Digital Downloads

If you want to run a store that offers  digital downloads, I recommend that you go with S3 for delivering your content.  I’ve dealt with traditional file hosting for years, and while it worked – I was on thin ice.

When you create the architecture of your store and the delivery of your digital media, you always want your store app to run on a different server than your digital downloads.  Keeping your app separate from gigs of files (as you grow) that could fill up the server is wise.  Separating the delivery from the app allows you to make updates without things breaking.

I used to use Dreamhost for hosting the files for the store, but I ran into a few things:

  1. TOS – You can’t just host files with them.  I looked, and this is true with most hosts.  This is the worst limitation.  And, I’ve been shut down before.
  2. Backups – Do it yourself, or it’s cost prohibitive for them to do it.
  3. Limits – If you go over your limit, you’re turned off.
  4. Downtime – One server has all your files, when it goes down….
  5. CDN – Create your own.  I mirrored servers using RSYNC.  It worked, but it was painful.
  6. Securing Files – Use .htaccess, or whatever you come up with.  No built in tokenization.
  7. Worry – There is a bit of worry.  Primarily, are my files still there?  Is that computer okay?

Now, I use S3, which works smoother:

  1. TOS – Simple Storage Service… takes any file you put up
  2. Backups – Why backup? It’s on the cloud
  3. Limits – No limit, you pay for what you get
  4. Downtime – Rare. I’ve seen amazon go down twice, for a few hours
  5. CDN – mmmm cloud
  6. Securing Files – Built in
  7. Worry – Much much less.  Really, is the cloud going to go down?  maybe… but if you are screwed, I’m pretty sure it’s not just you, it’s a network outage.

With S3, you pay for what you use, the prices are reasonable, and you don’t have to worry about your files being there.  I’m sold on S3 for delivering digital downloads.

Want to signup for S3 now? It’s fairly painless.  Go to http://aws.amazon.com/s3/ or click .  You’ll get access to your S3 account.  Create a bucket, and go!

No related posts.

6 Comments

  • nice write-up :)

  • S3 is not a CDN. That’s why AWS has started offering CloudFront.

  • Chris Gratigny wrote:

    er, oops. at least “mmmm cloud” doesn’t say specifically that it is a CDN. I just like that it isn’t on one server in one place that I have to worry about. at least I don’t think I do.

  • Definitely! And, if you’re in the Washington state area it’s probably about as good as a CDN ;)

  • How are you finding the cost of S3? I am considering it for storing images and maybe even js/css files…

    What do you reckon?

  • The cost for small files is very minimal, we have the downloads for the store hosted there and are only paying <$100 a month. We’re considering putting all of the images for iBethel.TV on S3 so Apache gets hit less. For the amount of CPU you save on your main app server, I think the cost of S3 is very reasonable.

Post a Comment

Your email is never shared. Required fields are marked *