Okay, I'm more of a coder, and not as familiar when it comes to things like system setup, though I try my best. I'm currently using Slicehost (stats below) to run a personal website that gets an okay amount of traffic.
- Linux (Ubuntu 8.04.2)
- 512MB RAM
- Avg. xfer = 4.85GB (0.68 in / 4.17 out)
- Automatic backups
I pay $48/month ($38 for hosting, $10 for backups).
I'm in the process of a site redesign, and with it, I'd like to move to AWS (EC2 & S3). I'm trying to figure out a similar (probably a little better in terms of RAM since I've consistently had high root & swap IO usage) setup, and how much that'll cost me.
Amazon offers a simple monthly calendar, but I'm not sure I'm entering the right info both in terms of finding a comparable setup, as well as what the price is coming out to be.
Relevant info about the new version of my website:
- Ruby (REE 1.8.7) / Rails 3.1
- PostgreSQL 9.0.4
- SearchSphinx (2.0) is required to be running in the background
- Various other cron jobs and rake tasks will be added as the app matures
- App allows users to upload images as part of their profiles, which I'm planning on storing in S3
For comparison, the current version of my website running on Slicehost:
- PostgreSQL 8.3
- Apache, DB, and files (images) all stored on same system
I guess my questions come down to:
- Do I want an on-demand instance, or a reserved instance? I assume reserved, but that made the price jump into the thousands for just 1 instance.
- According to the AWS instance types, I can probably settle for a Micro (613MB RAM) or Small (1.7GB RAM) instance. Does that sound right?
- I have no clue what numbers I want numbers to put into the EBS volumes part of the calculator, if anything. Do I even need an EBS volume, or will my EC2 instance have space that will be sufficient? (Keep in mind I'm offloading my user-uploaded photos to S3.)
I guess that's about it. When I try to make some rough estimates of what I assume is about right, it comes out to $63/month with a $350 setup fee. (This also doesn't include any of the S3 expenses.) I'm assuming the additional cost will be well worth the pain it will solve me in the long run, but I'm not even sure I'm putting the "right" numbers in the calculator in the first place.