Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It is (of course) an EBS backed instance; I would like to see what the impact of having increased CPU power would do for it. What's the easiest way?

share|improve this question

The biggest caveat to this is that an m1.small is a 32-bit machine whereas a t1.micro is a 64-bit machine. Unless you're running a 32-bit AMI on the micro, you won't be able to upgrade to m1.small. You'll have to skip up to the next level where 64-bit is again supported.

share|improve this answer
m1.smalls are now available as 64-bit: – Derek Dahmer Sep 20 '12 at 17:18
up vote 1 down vote accepted is the answer

share|improve this answer

Once you change the instance type by stoping the instance and changing instance type, reassociate your elastic IP to that instance. And then:

you need to restart your mysqld and httpd.conf.

sudo /etc/init.d/mysqld restart sudo /etc/init.d/httpd restart

share|improve this answer
There's no need to restart mysql/httpd. Stopping the instance handles that just fine. – ceejayoz Sep 3 '13 at 14:56
I guess it was just mysqld. I had to restart that to get may amazon webserver to work, after I changed the instance type from small to micro – coolcool1994 Sep 3 '13 at 16:02
You may just not have your MySQL set to start on boot. – ceejayoz Sep 3 '13 at 16:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.