EC2 Quick Start
- sign up
- generate cert & private key
- download amazon ec2 tools into ~/ec2
- export environment variables
- export EC2_HOME=~/ec2
- export JAVA_HOME=/usr/java/jre1.5.0_15
- export EC2_PRIVATE_KEY=~/ec2/pk.pem
- export EC2_CERT=~/ec2/cert.pem
- export EC2_JVM_ARGS=”-Dhttps.proxyHost=my.proxy -Dhttps.proxyPort=8080″
Then run amazon ec2 describe images utility
$ ./bin/ec2-describe-images -a
you’ll see a list of over 600 AMIs including the following jumpboxs
- IMAGE ami-70ab4f19 jumpbox-amis/bugzilla-1.1.0.manifest.xml
- IMAGE ami-71ab4f18 jumpbox-amis/mediawiki-1.1.0.manifest.xml
- IMAGE ami-6aac4803 jumpbox-amis/movabletype-1.1.0.manifest.xml
- IMAGE ami-0eb45067 jumpbox-amis/wordpress-1.1.0.manifest.xml
just choose a JumpBox AMI virtual machine software appliance and run it !
Finally check your credit card bill the following month !
Red Hat has partnered with Amazon to provide publicly accessible servers, bandwidth, storage, and Red Hat Enterprise Linux and/or JBoss Enterprise Application Platform on a monthly/hourly basis.
This dynamic set of compute resources allows you to scale your compute resources up and down as your needs change, without upfront investment in hardware or software.
You can now run JumpBoxes on Amazon’s Elastic Compute Cloud (EC2). Amazon EC2 can be thought of as a big virtualization system in the internet cloud that you pay for by the hour. So instead of running a JumpBox on your hardware you use Amazon’s hardware and just pay for what you need.
There are four beta JumpBox AMIs:
- JumpBox for MediaWiki – AMI: ami-71ab4f18
- JumpBox for WordPress – AMI: ami-0eb45067
- JumpBox for Movable Type – AMI: ami-6aac4803
- JumpBox for Bugzilla – AMI: ami-70ab4f19
These are currently available as public AMIs on the Amazon system so if you have an Amazon EC2 account you should be able to launch them using any tool that can launch EC2 instances. If you don’t have an Amazon EC2 account you can easily signup for one using any Amazon account.
Just noticed an interesting quirk with VMWare Server and hyper threading CPUs
I told my VM to use 1 CPU but CentOS 4 install detected the underlying hardware CPU had hyper threading so installed the SMP kernel !
Linux localhost.localdomain 2.6.9-67.0.15.ELsmp #1 SMP Thu May 8 10:52:19 EDT 2008 i686 i686 i386 GNU/Linux
as opposed to creating a VM where underlying hardware didn’t have hyper threading where CentOS 4 install just installed the basic kernel !
Linux localhost.localdomain 2.6.9-67.0.15.EL #1 Thu May 8 10:39:19 EDT 2008 i686 i686 i386 GNU/Linux