--- wikisrc/amazon_ec2.mdwn 2011/02/19 04:34:56 1.23 +++ wikisrc/amazon_ec2.mdwn 2011/02/25 00:35:09 1.35 @@ -79,7 +79,55 @@ AKI, or *Amazon Kernel Image*, are a spe # Using pre-made AMIs -XXX TODO +The following AMIs are publicly available. You can use them to [start a NetBSD instance](#index11h2) quickly, without needing to build your image by hand. + + + + + + + + + + + + + + + + + + + + + + + +
NetBSD versionus-west-1us-east-1eu-west-1ap-southeast-1
NetBSD 5.1.0_PATCH + 32 bits:
+ 64 bits: + 		+ 32 bits:
+ 64 bits: ami-f612e19f + 		+ 32 bits:
+ 64 bits: + 		+ 32 bits:
+ 64 bits: +
NetBSD-HEAD (5.99.45) + 32 bits:
+ 64 bits: + 		+ 32 bits:
+ 64 bits: + 		+ 32 bits:
+ 64 bits: + 		+ 32 bits:
+ 64 bits: +
# Build-up your NetBSD system @@ -104,7 +152,7 @@ cd src ./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 +164,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 +175,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=":" @@ -196,12 +246,12 @@ 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* 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): +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/ @@ -218,7 +268,7 @@ $ gzip -9n NetBSD-AMI.img # Upload NetBSD to EC2 -We must now upload our NetBSD system to EC2. For that, we will have to create a minimalist EC2 instance, to which we will copy our files to construct our snapshots. For that, we will use an Amazon Linux AMI instance. +We must now upload our NetBSD system to EC2. For that, we will have to create a minimalist EC2 instance, to which we will copy our files to construct our snapshots. We will use an Amazon Linux AMI instance. EC2 being localized in geographical regions, you have to carefully choose the AMI identifier you want to use there. This depends on where you want to execute your instance. Amazon Linux AMI IDs are listed on [the main page](http://aws.amazon.com/amazon-linux-ami/) of the project, by regions. Choose ones backed by EBS. @@ -226,7 +276,7 @@ The examples listed here assume that the ## Create an Amazon Linux instance -Creating an instance straightforward. Amazon provides [different types of instances](http://aws.amazon.com/ec2/pricing/), with varying levels of billing and reliability. We will use a [*micro* instance](http://aws.amazon.com/ec2/faqs/#How_much_compute_power_do_Micro_instances_provide); its pricing is almost free. +Creating an instance is straightforward. Amazon provides [different types of instances](http://aws.amazon.com/ec2/pricing/), with varying levels of billing and reliability. We will use a [*micro* instance](http://aws.amazon.com/ec2/faqs/#How_much_compute_power_do_Micro_instances_provide); its pricing is almost free. [[!template id=programlisting text=""" $ ec2-run-instances ami-74f0061d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME @@ -276,12 +326,12 @@ 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 """]] -We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img*, to our instance host: +We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img.gz*, to our instance host: [[!template id=programlisting text=""" # Upload kernel to Linux AMI @@ -375,7 +425,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 ***