Just wanted to follow up on my previous post in regards to how to resize the root partition of an EC2 instance. Turns out that, once you’ve edited the root partition while in the launch panel, you can then perform the resize command right away, as soon as the instance is up and running and you have ssh’ed to it.
[root@ip-aa-bb-cc-dd ~]# resize2fs /dev/xvde1
This is definitely better than what I thought one had to do to get a bigger root partition.
Today I was playing with EC2, trying to launch a RHEL 6.3 instance so that I could then install the latest version of Katello and beat a bit on it… just for fun, you know? Using the EC2 Management Console web interface I used the “classical” wizard to select all the components I wanted for a m1.large instance, making sure to edit the default 7.5 GB root partition they give you so that I could have more space available to synchronize content… but when the instance finally came up I realized that my disk space was still showing the default value:
You probably remember reading about my issues with running my WordPress-based blog on Dreamhost's environment, and how frustrated I was with the experience of using their Private Server services. The short version is that I eventually migrated my blog back to their shared hosting environment, turned off most of the plugins and cried myself to sleep.
The very next day, after reading (and replying to) the comments I received, one in particular caught my eye: Amazon’s Free Usage Tier offering new customers the following EC2 services each month for one year: