Migrating from Amazon Web Services to Linode

Well, I’m not sure what you did with your Friday night, but I’ve spent the last few hours migrating websites from my Amazon Web Services instance to a virtual server at Linode. I’ve experimented with AWS for just over a year now, but the simple fact is that running multiple sites in a micro instance was just not a good idea. My micro instance would hit CPU throttling after less than a minute of CPU use, and then would be cut back to 2% CPU usage. I knew this limitation going in to AWS, but it finally became too big a hassle.

Cindy and I run a total of seven sites. None of them are particularly high traffic, and I’m sure we would be fine in a small instance at AWS. Unfortunately, a small instance is a lot more money. A Linode node is about the same price, but the customer service at Linode is what really pushed me over the edge.

I run a Tor relay on Linode that I’ve secured fairly heavily. The few times I’ve noticed another Linode customer scanning my system or had some other technical issue, the Linode support staff have been extremely responsive. But best of all, not only are they timely, you actually talk to someone who knows what the fuck is going on. As much as I admire automation, I have to admit it’s very comforting to know that if I email Linode tonight, I’ll have an actual technical person replying to me by the morning (and they’re likely to have already fixed the issue).

Now, in the grand scheme of things, Linode is not really competing against AWS. AWS is all about automated provisioning and large scale rapid development. Linode doesn’t have anywhere near the provisioning and deployment features AWS has. But that’s ok. I’m not trying to rapidly scale up to handle millions of customers, I’m just trying to run a few blogs.

Another migration that I’m part way through is moving our systems into CloudFlare for security and acceleration. Unfortunately, getting self-signed SSL certificates and WordPress to play well with the free version of CloudFlare is proving to be tricky. Once I get the wrinkles ironed out, that’ll be another blog post.

If you’re looking for a server host, and want to support Cindy’s & my websites, use our Linode referal link!

3 thoughts on “Migrating from Amazon Web Services to Linode

  1. Hi
    I represent Incapsula, like CF we provide CDN + security services (complete with PCI compliant WAF).
    While using custom SSL with CF will cost you 200$ a month you can get the same features here for 9$ a month and with zero limitations.
    Check us out.

  2. Hey Igal,

    Thanks for the info on your service! Just FYI, for seven sites, CF would cost $50/month ($20 first site + 6 * $5 secondary sites). But that is for wild card SSL certificates. The $200/month you quoted is for custom SSL certificate support, but that’s really overkill for any small shop. The only reason you’d want their custom SSL support is if you had an EV certificate, but I can’t imagine anyone running a blog or even a small business site investing in an EV cert.

    You guys still have a compelling offer with your price point for a single site, but for seven sites you end up costing more ($63 vs $50).


  3. Hi Daniel,

    I’m an old friend of Cindy’s – I stumbled onto your blog and saw this post and it caught my attention. I used to design/develop Virtual Appliances for my previous employer and discovered AWS / EC2 .. It could be a pain, and was expensive.. But.. man I had fun learning that API for some reason 🙂

    But anyways, I may check out Linode and I’ll use that referral link. Take care!

    Brian W.

    btw – congrats on the recent wedding! 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

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