--- wikisrc/amazon_ec2.mdwn 2011/02/24 00:05:32 1.34 +++ wikisrc/amazon_ec2.mdwn 2011/03/03 23:07:49 1.39 @@ -84,24 +84,29 @@ The following AMIs are publicly availabl - - - - + + + + + + +
NetBSD versionus-west-1us-east-1eu-west-1ap-southeast-1us-east-1 (Virginia)us-west-1 (N. California)eu-west-1 (Ireland)ap-southeast-1 (Singapore)ap-northeast-1 (Tokyo)
NetBSD 5.1.0_PATCH 32 bits:
- 64 bits: + 64 bits: ami-06b4466f
32 bits:
- 64 bits: ami-f612e19f + 64 bits: ami-99f7a7dc
32 bits:
- 64 bits: + 64 bits: ami-cfa296bb +
+ 32 bits:
+ 64 bits: ami-04e49a56
32 bits:
@@ -126,6 +131,10 @@ The following AMIs are publicly availabl 32 bits:
64 bits:
+ 32 bits:
+ 64 bits: +
@@ -224,7 +233,6 @@ ec2_init() ) } - load_rc_config $name run_rc_command "$1" """]] @@ -254,7 +262,7 @@ 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 @@ -326,7 +334,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 """]]