--- wikisrc/amazon_ec2.mdwn 2011/02/22 22:47:51 1.25 +++ wikisrc/amazon_ec2.mdwn 2011/03/13 02:18:41 1.46 @@ -8,78 +8,11 @@ This tutorial aims at showing how you ca If you already have an account for [Amazon Web Services](http://aws.amazon.com/), and you are a registered user for EC2 service, you can directly jump to section [What do you need to know](#index2h2). If not, keep reading. -## Quick overview - -Before you can start playing with Amazon EC2, you have to create an account on Amazon Web Services, of which EC2, the Elastic Compute Cloud, is part. This is fairly straightforward, and done in two steps: - -1. you "sign-up" directly on [Amazon Web Services](http://aws.amazon.com/) home-page. This is where you enter your credentials, and confirm your AWS account registration. -1. you sign-up to EC2 through [EC2 AWS home-page](http://aws.amazon.com/ec2/). You will be asked some more information, like a credit card (for billing), and a phone-number, for account validation. - -## What do you need to know? - -EC2 uses different types of credentials. In addition to your login and password, you need an access key, a X.509 certificate (with its private key), and a pair of RSA keys, for remote SSH access. - -These can be created through the [Security Credentials](https://aws-portal.amazon.com/gp/aws/developer/account/index.html?ie=UTF8&action=access-key) page (also accessible from the [Account](http://aws.amazon.com/account/) page): - -1. create the access key. Keep a secured copy of the ID and its associated secret value. These will be used by various scripts later on to perform certain EC2 actions. -1. note down your account number (different from your access key ID!). This identifier can usually be obtained in the right top part of the page; it is a serie of numbers, separated with dashes: XXXX-XXXX-XXXX. -1. create, or upload, a X.509 certificate, in PEM format. Keep the private key in a safe place. -1. lastly, generate Amazon EC2 key pairs that will be used for SSH access. This step will be performed through the [Amazon Management Console](https://console.aws.amazon.com/ec2/home). Note down the SSH Key Pair Name you chose. - -### Keep your credentials! - -The different credentials created above will be used in various places of EC2, and by a myriad of commands. You are advised to keep them easily accessible, while still reasonably secure regarding their access. Most EC2 tools expect them to be find through a set of environment variables. - -For convenience, you could store them under a *.ec2* directory inside your *$HOME*: - -[[!template id=programlisting text=""" -$ ls .ec2/ -cert-SOMERANDOMKEY.pem # the X.509 certificate -id_rsa.ec2 # private RSA SSH key -id_rsa.ec2.pub # public RSA SSH key -pk-SOMERANDOMKEY.pem # the private key associated to the certificate -"""]] - -then set the environment accordingly: - -[[!template id=programlisting text=""" -export EC2_PRIVATE_KEY=$HOME/.ec2/pk-SOMERANDOMKEY.pem -export EC2_CERT=$HOME/.ec2/cert-SOMERANDOMKEY.pem -export EC2_SSH_KEY=$HOME/.ec2/id_rsa.ec2 -export EC2_SSH_KEYNAME=<your_ssh_key_pair_name> -export EC2_ACCOUNT_NUM=XXXX-XXXX-XXXX -export EC2_ACCESS_KEY=MYACCESSKEYID -export EC2_SECRET_KEY=MYSECRETACCESSKEY -"""]] - -Please note that the rest of the tutorial will assume that these variables are set. - -## Installing EC2 API tools - -NetBSD provides EC2 API tools, to ease EC2 account management a little bit. The package is found inside [pkgsrc](http://www.pkgsrc.org), under [[!template id=pkg category=misc name=ec2-api-tools]]. - -[[!template id=programlisting text=""" -cd /usr/pkgsrc/misc/ec2-api-tools -make ACCEPTABLE_LICENSES+=amazon-software-license install -"""]] - -Package depends on Java, so build will take some time to finish. While it builds, just continue reading. - -## EC2 vocabulary -- last notes - -Before starting to play with EC2, you need to be familiar with the EC2 vocabulary used throughout this tutorial. - -Briefly said, EC2 uses [Xen](http://www.xen.org) as virtualization solution. So, in essence, all operating systems that support Xen para-virtualization can theoretically run inside EC2, as a domU. This is the case for NetBSD; however, please note that only amd64 is currently supported. Work is on-going to support 32 bits for EC2. - -All operating systems are run as *instances*, which are, as their name implies, the instantiation of a specific AMI, or *Amazon Machine Image*. An AMI is an image built from specific *snapshots* of *volumes*. The volumes are part of [Elastic Block Storage](http://aws.amazon.com/ebs/) (or EBS for short), which is another service offered by AWS, distinct from EC2. - -These instances are tied to a *region* (a geographical location; typically US East, US West, Europe West, etc.). Each region has *availability zones*, which can be compared to a sub-region, each one being physically distinct from another. Regions are identified by a name, like *us-east-1*, *eu-west-1*. Same goes for availability zones, usually with the region's name as prefix: *us-east-1a*, *us-east-1b*, and so forth. Note that resources are **not** shared between zones, so if you transfer data from one zone to another, you will be charged for it. - -AKI, or *Amazon Kernel Image*, are a specific type of image. It represents the Xen guest para-virtualized kernel, as used by an AMI. Certain AKIs are allowed to boot customized operating systems, e.g. those that are still not officially supported by Amazon. Thanks to [PyGrub](http://wiki.xensource.com/xenwiki/PyGrub), it can boot a kernel that resides inside an AMI's snapshot. +[[!inline pages="amazon_ec2/first_steps" raw="yes"]] # Using pre-made AMIs -XXX TODO +[[!inline pages="amazon_ec2/AMIs" raw="yes"]] # Build-up your NetBSD system @@ -101,10 +34,10 @@ ftp -a 'http://ftp.netbsd.org/pub/NetBSD tar -xzpf src.tar.gz cd src # build distribution and kernel -./build.sh -O ../obj -T ../tools -D ../dest -R ../release -V INSTALLSETS="base etc" -m amd64 -U distribution +./build.sh -O ../obj -T ../tools -D ../dest -R ../release -m amd64 -U distribution ./build.sh -O ../obj -T ../tools -m amd64 kernel=XEN3_DOMU # install distribution in /mnt/ec2 -./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U install=/mnt/ec2 +su root ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U -V INSTALLSETS="base etc" install=/mnt/ec2 """]] # Configuration of your NetBSD EC2 tree @@ -116,6 +49,7 @@ Under */mnt/ec2*, edit the files to add [[!template id=filecontent name=etc/rc.conf text=""" rc_configured=YES +ec2_init=YES sshd=YES # for remote shell access to instance """]] @@ -126,16 +60,17 @@ PermitRootLogin without-password This file is needed if you want to login via the EC2 SSH key pair created previously: -[[!template id=filecontent name=etc/rc.d/ec2-init text=""" +[[!template id=filecontent name=etc/rc.d/ec2_init text=""" #!/bin/sh # -# PROVIDE: amazon-ec2 +# PROVIDE: ec2_init # REQUIRE: NETWORKING # BEFORE: LOGIN $_rc_subr_loaded . /etc/rc.subr name="ec2_init" +rcvar=${name} start_cmd="ec2_init" stop_cmd=":" @@ -174,7 +109,6 @@ ec2_init() ) } - load_rc_config $name run_rc_command "$1" """]] @@ -196,15 +130,15 @@ ptyfs /dev/pts ptyfs rw procfs /proc procfs rw EOF # EC2 startup script (if you installed it) -if [ -f etc/rc.d/ec2-init ]; then - chmod 755 etc/rc.d/ec2-init +if [ -f etc/rc.d/ec2_init ]; then + chmod 555 etc/rc.d/ec2_init fi """]] You can then proceed to modifying the system living under */mnt/ec2*, so it can fit your needs (adding custom binaries, packages, etc). When done, build the *NetBSD-AMI.img.gz* ffs image, via [[!template id=man name=makefs section=8]], or **nbmakefs**, from the [toolchain](http://www.netbsd.org/docs/guide/en/chap-build.html#chap-build-tools): [[!template id=programlisting text=""" -$ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k NetBSD-AMI.img /mnt/ec2/ +$ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k /tmp/NetBSD-AMI.img /mnt/ec2/ Calculated size of `NetBSD-AMI.img': 268435456 bytes, 7345 inodes Extent size set to 8192 NetBSD-AMI.img: 256.0MB (524288 sectors) block size 8192, fragment size 1024 @@ -276,7 +210,7 @@ ATTACHMENT vol-24f88d4c i-5babe7 Before we can connect to our brand new instance, we have to allow connections on SSH port (22) through the AWS EC2 firewall: [[!template id=programlisting text=""" -$ ec2-authorize default -p 22 +$ ec2-authorize default -p 22 --region us-east-1 GROUP default PERMISSION default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0 """]] @@ -375,7 +309,7 @@ IMAGE ami-74d0231d You can now start your own NetBSD instance, via: [[!template id=programlisting text=""" -$ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c +$ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME RESERVATION r-08218465 983624114127 default INSTANCE i-953d72f9 ami-74d0231d pending 0 t1.micro 2011-02-18T02:05:46+0000 us-east-1c aki-4e7d9527 monitoring-disabled *** Wait a few minutes, micro instances take time to start ***