I know that I’ve mentioned how I’ve been hosting my blog and sister’s website on a virtual server within the Amazon Web Services (AWS) cloud. Well, recently (past month or so), they announced that they opened a new region in Oregon. Before this, there were only two regions in the US, east and west. The east region is in Virginia. The west is in California. Thing was (and still is) is that the California region is just a bit more expensive. That’s not really a big deal when I’m running on the Free Tier for a year, but at the time, I’d have to start paying per-the-hour, and the east region (Virginia) was the cheapest, so I chose that region.
Well, when the Oregon region opened up, along with a new “reserved instance” where I can reserve an instance for 3 years at the price of 9 months, (36 > 9), I decided I wanted to move my server. A few quick tests proved that I’d benefit from shorter pings (think round-trip time for a small message to be responded to). The only thing was that you can’t just “move” a server, even a virtual server, across regions without some work.
So today, I finally took the time to start up a new instance in Oregon, transfer all of my data and configuration files, export/import my database, and change the DNS records. Now that’s really the only thing I’m waiting on. Turned out that moving a web server is pretty painless if you don’t over complicate things. Only took me a couple hours.
Anyway, that’s a lot of technical mumbo-jumbo. In other news, school start tomorrow, although my classes don’t start until Thursday. I’m just hoping to survive this semester. Somehow I managed to pull a B- out of one of my classes last semester, despite missing a couple homework assignments and bombing the final. It’s a Christmas miracle! (P.S. I love having my blog snow again!)
Currently listening to: “For the Beauty of the Earth” played by Sav
It’s been a busy couple weeks. I’m crazy busy with only two classes, which I can’t understand. I basically have to steal free time, which is a relief, although it makes me feel guilty because I’m not quite caught up in one of my classes.
But the good news: there is a light at the end of the tunnel. Actually two lights.
First, the end of the semester will come, and I’ll get to work doing research in networking. A welcome change. I haven’t yet told my boss. But I don’t feel bad, because he has been planning on having me work on the worst projects. And I’d rather not.
Second, someday, when I again find free time, I’m going to take an awesome design my sister created for a website and actually make it into a website. And when I do that, I’ll be moving my own stuff to the same server. YAY.
Nerdy details, but I’m planning on hosting my server through Amazon Web Services and their Elastic Cloud. Unless I pass the free tier, then I’m going to have to rethink my plan.
I’ve also been quite torn about whether or not I want to blog more about my CS 462 class and my work there. I actually do want to blog it, but a lot of the students have adopted the, “I just want to follow the TA’s examples and code, and I don’t want to work anything else on my own,” mentality. Hence, I’m reluctant.
Anyway, the wife is telling me that we should leave. I’m agreeing.
This will guide you though creating a customized AMI on Amazon EC2.
This is mostly for the benefit of those in the class who read this post. I’m writing this mostly as a tutorial instead of a “what I did” because I’m only going to give enough instruction to get something running, not tell you all the tinkering I did. I also apologize for the varying tense of the writing. Some steps got written before and some after I had actually done them. Continue reading Customizing an AMI on Amazon EC2…
After days of frustrating work, I finally found the cause of all my woes:
Turns out that Ubuntu/Canonical put a forward-thinking update into the file system table, but didn’t realize that the bundling tool for re-bundling an instance would fail because of this.
Luckily, the page above also has the fix.
This is definitely going into my tutorial…
After working for 3 days, learning EC2 and how to bundle my own AMI, setting up the environment the way I want, tinkering for hours, I sadly clicked terminate on my instance, because no matter how many times I bundled it, I couldn’t log in to the new instance once launched.
But luckily, I’ve been documenting the whole way, so the second time around should take much less time.
I’m curious to know how close others have gotten. Hopefully having a bit more luck than me. I’m hoping to be done by class today.
I’ll be posting a lot about what I’m doing in my CS 462 class here on tumblr. This will give me a good chance to test out tumblr and see how it compares to WordPress.
On that note, I’m excited to test out markdown. It’s a pearl script (ported to PHP) that converts plain text into HTML using a special syntax.
Our class is pretty open ended. We can use any OS and any language to complete the labs. The TA is using (and as such, it is recommended that we use) Ubuntu Linux and Python. I’m going to use Ubuntu also, but I think that I am going to use PHP. There’s two reasons:
- I know PHP, and I don’t know Python.
- People in the class are using PHP, and Steven, the TA, might want someone to bounce questions off of.
Anyway, I should be starting on the first lab today. We’ll see how that goes. Hopefully this gets added to the class planet before I publish my next post.