"Restarting" the Virtual Machine

You can't actually restart it, instead you essentially delete it and roll-back to a prior machine image.

1. Use the EC2 Console to terminate the instance.
2. Still in the console, locate the machine image you want to roll back to and Launch an instance of that image.
   1. This post may provide some guidance as to which image to launch.
   2. Specify the details of the instance, we usually create one small instance, use the StandardFirewallRules Security Group, and the BaseAdmin key-pair.
3. Attach the appropriate Elastic Block Store to the new instance at /dev/sdh.
4. Follow the directions below to connect to the instance via SSH.
5. Follow the directions below to mount the Elastic Data Store.
6. Follow the directions below to start Apache, then PostgreSQL and MySQL, then Tomcat.

Connect to the Instance Using SSH (and PuTTY)

If you already have the .ppk file for the appropriate user that you wish to log in with, use it. You may want to set up SSH Tunneling if you want to use pgAdmin to connect to PostgreSQL.

If you don't have a.ppk file, follow the instructions outlined in this post.

Mounting the Elastic Block Store

First, use the EC2 Console to attach the volume to the instance at /dev/sdh

mkdir /mnt/data-store
mount /dev/sdf /mnt/data-store

Starting, Stoping, Restarting Applications

These commands should be executed with root privileges

/etc/init.d/apache2 start
/etc/init.d/apache2 stop
/etc/init.d/apache2 reload

/etc/init.d/tomcat6 start
/etc/init.d/tomcat6 stop
/etc/init.d/tomcat6 restart

/etc/init.d/postgresql-8.4 start
/etc/init.d/postgresql-8.4 stop
/etc/init.d/postgresql-8.4 restart

/etc/init.d/mysql start
/etc/init.d/mysql stop
/etc/init.d/mysql restart