...
Gallery | ||||
---|---|---|---|---|
|
...
Steps to fire VM & ssh to it (after you set up all credentials)
- login to AWS page
- select: Amazon Elastic Compute Cloud
- TOP-UP: 'Your Account' , select 'AWS Management Console'
- TOP-UP-Yellow: 'Sign in to AWS console'
- 'Lunch Instances'
- select type of VM (e.g. Fedora for regular linux), press select
- in lunch wizard 'Skip this'
- select # of machines & CPU power (star with 1, small)
- in 'Key Pair Name' select ssh Keys you have created earlier
- if you want output to survive after VM is shut down in options select: Availability Zone & remember it
- press 'Lunch' at the bottom
Now find it, it is beta-version, pressing 'Refresh' screen in the browser may help
- to ssh to this machine you need to know:
- Public DNS, sth like: ec2-75-101-246-229.compute-1.amazonaws.com
- absolute path to your ssh keys, e.g. janAmazonKey.pem
- from the local prompt execute:
ssh -i ~/janAmazonKey.pem root@ec2-75-101-246-229.compute-1.amazonaws.com
...
- On the left, go to 'Security Groups'
- select 'default' fire wall (unless you have sth else already)
- add & save : SSH tcp 22 22 0.0.0.0
- now try ssh again
...
Mounting EBS (permanent) volume to the instance (it was not reliable for me, between sessions data were partially corrupted)
- 1st time it need formating
- Browser: Create volume , using 'Volumes', pick 300GB (it is small and not pricy)
- Browser: right click on the volume, attache it to running Instance of VM, remember name, e.g.: /dev/sdf
- ssh to VM
- partition this disk , e.g. using fdisk
- fdisk /dev/sdf
n : new partition
p : primary
1 : partion #1
1 : (default begin)
enter : (default end)
p : print
w : write partition
- fdisk /dev/sdf
- format disk using mkfs
mkfs.ext3 /dev/sdf1 ('1' is partition selected earlier)
agrre on any question by pressing 'enter' - mount disk as home dir named storage
mkdir /storage
mount /dev/sdf1 /storage
cd /storage
ls
SCP file from AMI to local machine
- partition this disk , e.g. using fdisk
scp -i ~/janAmazonKey.pem root@ec2-174-129-63-11.compute-1.amazonaws.com:"/bla_lis" .
...
|
...
Bundling & registering AMI
It works the best in a machine w/ installed Java and some EC2 software. This is reasonable instruction:http://www.linuxconfig.org/Howto_CREATE_BUNDLE_UPLOAD_and_ACCESS_custom_Debian_AMI_using_ubuntu
It is written for Ubuntu 9.04 machine, so I selected this VM:
ami-2bfd1d42 binarymillenium/ec2/ubuntu/version2/image.manifest.xml
and added the following:
next I added:
mkdir ~/aws
cd ~/aws
wget http://s3.amazonaws.com/ec2-downloads/ec2-api-tools.zip
wget http://s3.amazonaws.com/ec2-downloads/ec2-qmiami-tools.zip
sudo unzip -d /opt/ ec2-api-tools.zip
sudo unzip -d /opt/ ec2-ami-tools.zip
export PATHEC2_HOME=$PATH:/opt/ec2-api-tools-1.3-3454442584/
export PATH=$PATH:$EC2_HOME//bin/ (but version # was different)
export
export JAVA_HOME=/usr/
If c-shell is used do:
Code Block |
---|
setenv EC2_HOME |
...
/opt/ec2-api-tools-1.3- |
...
46266/ setenv PATH $PATH":$EC2_HOME |
...
/ |
...
bin/" |
Now I was able to test the following command does sth
ec2-register
...
- Register Image at EC2
ec2-register star-sl08b-s3-bucket/star-sl08b-image.manifest.xml
Conversion of VMware to EC2
http://thewebfellas.com/blog/2008/9/1/creating-an-new-ec2-ami-from-within-vmware-or-from-vmdk-files