Annotation of wikisrc/amazon_ec2.mdwn, revision 1.21
1.1 wiki 1: [[!toc]]
2:
3: # Introduction
4:
1.21 ! wiki 5: This tutorial aims at showing how you can build, setup, upload and launch NetBSD under the [Amazon EC2](http://aws.amazon.com/ec2/) service. We will first give some brief explanations on how you can obtain an AWS account, and what you will need to run NetBSD under EC2. Then, at your convenience, you will be able to start with pre-made images, or roll-out your own.
1.1 wiki 6:
1.3 wiki 7: # Subscribe to AWS (Amazon Web Services)
8:
9: 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.
1.1 wiki 10:
1.3 wiki 11: ## Quick overview
1.1 wiki 12:
1.3 wiki 13: 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.1 wiki 14:
1.3 wiki 15: 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.
16: 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.
1.1 wiki 17:
1.16 wiki 18: ## What do you need to know?
1.1 wiki 19:
1.3 wiki 20: 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.
21:
22: 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):
23:
24: 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.
25: 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.
26: 1. create, or upload, a X.509 certificate, in PEM format. Keep the private key in a safe place.
1.9 wiki 27: 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.
1.3 wiki 28:
1.1 wiki 29: ### Keep your credentials!
30:
1.3 wiki 31: 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.
32:
1.9 wiki 33: For convenience, you could store them under a *.ec2* directory inside your *$HOME*:
1.3 wiki 34:
35: [[!template id=programlisting text="""
36: $ ls .ec2/
37: cert-SOMERANDOMKEY.pem # the X.509 certificate
1.5 wiki 38: id_rsa.ec2 # private RSA SSH key
39: id_rsa.ec2.pub # public RSA SSH key
1.3 wiki 40: pk-SOMERANDOMKEY.pem # the private key associated to the certificate
41: """]]
42:
43: then set the environment accordingly:
44:
45: [[!template id=programlisting text="""
46: export EC2_PRIVATE_KEY=$HOME/.ec2/pk-SOMERANDOMKEY.pem
47: export EC2_CERT=$HOME/.ec2/cert-SOMERANDOMKEY.pem
48: export EC2_SSH_KEY=$HOME/.ec2/id_rsa.ec2
1.9 wiki 49: export EC2_SSH_KEYNAME=<your_ssh_key_pair_name>
1.3 wiki 50: export EC2_ACCOUNT_NUM=XXXX-XXXX-XXXX
51: export EC2_ACCESS_KEY=MYACCESSKEYID
52: export EC2_SECRET_KEY=MYSECRETACCESSKEY
53: """]]
54:
55: Please note that the rest of the tutorial will assume that these variables are set.
56:
1.16 wiki 57: ## Installing EC2 API tools
1.9 wiki 58:
59: 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]].
60:
61: [[!template id=programlisting text="""
62: cd /usr/pkgsrc/misc/ec2-api-tools
63: make ACCEPTABLE_LICENSES+=amazon-software-license install
64: """]]
65:
66: Package depends on Java, so build will take some time to finish. While it builds, just continue reading.
67:
1.16 wiki 68: ## EC2 vocabulary -- last notes
1.3 wiki 69:
70: Before starting to play with EC2, you need to be familiar with the EC2 vocabulary used throughout this tutorial.
71:
72: 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.
73:
74: 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.
1.1 wiki 75:
1.9 wiki 76: 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.
77:
1.3 wiki 78: 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.
1.1 wiki 79:
1.17 wiki 80: # Build-up your NetBSD system
1.1 wiki 81:
1.6 wiki 82: ## Fetch and build NetBSD
1.1 wiki 83:
1.6 wiki 84: EC2 does not provide direct access to console. As a consequence, we cannot rely on it for installation, especially via [[!template id=man name=sysinst section=8]]. We must therefore build and install NetBSD in a separate directory, and configure it manually, before upload.
1.1 wiki 85:
1.9 wiki 86: This tutorial assumes that you will build the system under */mnt/ec2*.
1.1 wiki 87:
1.21 ! wiki 88: /!\Please note that you will need the [[!template id=man name=makefs section=8]] tool later in the process, so you can build a file system image that can be uploaded to Amazon EC2. You are therefore advised to perform the installation directly under a living NetBSD system, or in case your are not, to fetch the *src* tree to build the toolchain, which will contain the **nbmakefs** utility.
1.1 wiki 89:
1.21 ! wiki 90: [Details regarding on how you can fetch *src* are given in the NetBSD's guide](http://www.netbsd.org/docs/guide/en/chap-fetch.html). Here are the basic commands you should type to build and install NetBSD under */mnt/ec2*:
! 91:
! 92: [[!template id=programlisting text="""
! 93: # fetch src.tgz
! 94: # decompress
! 95: # build toolchain, kernel and distribution
! 96: # install in /mnt/ec2
! 97: """]]
1.6 wiki 98:
1.16 wiki 99: # Configuration of your NetBSD EC2 tree
1.6 wiki 100:
1.9 wiki 101: /!\This part assumes that you have a non-configured NetBSD system extracted under */mnt/ec2*; that is, it should have not been modified through [[!template id=man name=sysinst section=8]], nor by you.
1.6 wiki 102:
1.9 wiki 103: Under */mnt/ec2*, edit the files to add (or modify) these lines:
1.6 wiki 104:
105: [[!template id=filecontent name=etc/rc.conf text="""
106: rc_configured=YES
107:
108: hostname=NetBSD-EC2-$(uname -m)
109: sshd=YES # for remote shell access to instance
110: """]]
111:
112: [[!template id=filecontent name=etc/ssh/sshd_config text="""
113: # Allows root to login via authentication keys
114: PermitRootLogin without-password
115: """]]
116:
1.21 ! wiki 117: This file is needed if you want to login via the SSH key pair created previously:
! 118:
! 119: [[!template id=filecontent name=etc/rc.d/ec2-init text="""
! 120: #!/bin/sh
! 121: #
! 122: # PROVIDE: amazon-ec2
! 123: # REQUIRE: NETWORKING
! 124: # BEFORE: LOGIN
! 125:
! 126: $_rc_subr_loaded . /etc/rc.subr
! 127:
! 128: name="ec2_init"
! 129: start_cmd="ec2_init"
! 130: stop_cmd=":"
! 131:
! 132: SSH_KEY_URL="http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key"
! 133: SSH_KEY_FILE="/root/.ssh/authorized_keys"
! 134:
! 135: ec2_init()
! 136: {
! 137: (
! 138: umask 022
! 139: # fetch the key pair from Amazon Web Services
! 140: EC2_SSH_KEY=$(ftp -o - "$SSH_KEY_URL")
! 141:
! 142: if [ -n "$EC2_SSH_KEY" ]; then
! 143: # A key pair is associated with this instance, add it
! 144: # to root 'authorized_keys' file
! 145: mkdir -p $(dirname "$SSH_KEY_FILE")
! 146: cd $(dirname "$SSH_KEY_FILE")
! 147:
! 148: grep "$EC2_SSH_KEY" "$SSH_KEY_FILE"
! 149: if [ $? -eq 0 ]; then
! 150: echo "Setting associated SSH key pair."
! 151: echo "$EC2_SSH_KEY" >> "$SSH_KEY_FILE"
! 152: fi
! 153: fi
! 154: )
! 155: }
! 156:
! 157: """]]
! 158:
! 159: Create various files and directories:
1.6 wiki 160:
1.8 wiki 161: [[!template id=programlisting text="""
162: cd /mnt/ec2
1.21 ! wiki 163: # Add proc and kern directories
! 164: mkdir proc kern
! 165: # EC2 network configuration, via DHCP
! 166: echo "dhcp" > etc/ifconfig.xennet0
! 167: # Basic fstab entries
1.8 wiki 168: cat > etc/fstab << EOF
1.6 wiki 169: /dev/xbd1a / ffs rw 1 1
170: /dev/xbd0a /grub ext2 rw 2 2
171: kernfs /kern kernfs rw
172: ptyfs /dev/pts ptyfs rw
173: procfs /proc procfs rw
1.8 wiki 174: EOF
1.21 ! wiki 175: # EC2 startup script (if you installed it)
! 176: if [ -f etc/rc.d/ec2-init ]; then
! 177: chmod 755 etc/rc.d/ec2-init
! 178: fi
1.6 wiki 179: """]]
180:
1.9 wiki 181: 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):
182:
183: [[!template id=programlisting text="""
184: $ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k NetBSD-AMI.img /mnt/ec2/
185: Calculated size of `NetBSD-AMI.img': 268435456 bytes, 7345 inodes
186: Extent size set to 8192
187: NetBSD-AMI.img: 256.0MB (524288 sectors) block size 8192, fragment size 1024
188: using 5 cylinder groups of 53.88MB, 6896 blks, 1728 inodes.
189: super-block backups (for fsck -b #) at:
190: 32, 110368, 220704, 331040, 441376,
191: Populating `NetBSD-AMI.img'
192: Image `NetBSD-AMI.img' complete
193: $ gzip -9n NetBSD-AMI.img
194: """]]
1.1 wiki 195:
1.17 wiki 196: # Upload NetBSD to EC2
1.1 wiki 197:
1.9 wiki 198: 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.
199:
1.18 wiki 200: 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.
1.9 wiki 201:
202: The examples listed here assume that the instances run in **US East**, within the **c** zone (e.g. **us-east-1c**). To have a list of EC2 regions, you can use the command **ec2-describe-regions**, and **ec2-describe-availability-zones** for availability zones.
203:
1.17 wiki 204: ## Create an Amazon Linux instance
1.9 wiki 205:
206: 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.
207:
208: [[!template id=programlisting text="""
209: $ ec2-run-instances ami-74f0061d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
210: RESERVATION r-1ab61377 983624114127 default
211: INSTANCE <strong>i-5babe737</strong> ami-74f0061d pending <your_ssh_key_pair_name> 0 t1.micro 2011-02-17T23:15:04+0000 us-east-1c aki-427d952b monitoring-disabled ebs paravirtual xen
212: """]]
213:
214: Use the instance identifier **i-XXXXXXX** to query the instance state via **ec2-describe-instances**. It will take some time to launch:
1.6 wiki 215:
1.9 wiki 216: [[!template id=programlisting text="""
217: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
218: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
219: INSTANCE i-5babe737 ami-74f0061d <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong> ip-10-99-86-193.ec2.internal running <your_ssh_key_pair_name> 0 t1.micro 2011-02-17T23:22:37+0000 us-east-1c aki-427d952b monitoring-disabled 67.202.24.108 10.99.86.193 ebs
220: """]]
1.1 wiki 221:
1.17 wiki 222: ## Create and attach your NetBSD volumes
1.1 wiki 223:
1.9 wiki 224: We will have to create and attach two EBS volumes:
225:
226: 1. one to contain the Grub *menu.lst* config file, as well as the NetBSD kernel.
227: 1. the other one will contain the root file-system.
228:
229: [[!template id=programlisting text="""
230: <strong>ec2-create-volume -s 1 -z us-east-1c</strong> # 1GiB -- will be used for Grub and kernel
231: VOLUME vol-24f88d4c 1 us-east-1c creating 2011-02-18T00:06:21+0000
232: <strong>ec2-create-volume -s 5 -z us-east-1c</strong> # 5GiB -- will contain the root file-system
233: VOLUME vol-36f88d5e 5 us-east-1c creating 2011-02-18T00:06:32+0000
234: *** Wait until both volumes are marked as "available" ***
235: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
236: VOLUME vol-36f88d5e 5 us-east-1c available 2011-02-18T00:06:32+0000
237: VOLUME vol-24f88d4c 1 us-east-1c available 2011-02-18T00:06:21+0000
238: # Attach them under /dev/sdf and /dev/sdg respectively
239: <strong>ec2-attach-volume vol-36f88d5e -i i-5babe737 -d "/dev/sdf"</strong> # root file-system
240: ATTACHMENT vol-36f88d5e i-5babe737 /dev/sdf attaching 2011-02-18T00:13:53+0000
241: <strong>ec2-attach-volume vol-24f88d4c -i i-5babe737 -d "/dev/sdg"</strong> # Grub and kernel
242: ATTACHMENT vol-24f88d4c i-5babe737 /dev/sdg attaching 2011-02-18T00:14:02+0000
243: *** Wait until both volumes are "attached" ***
244: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
245: VOLUME vol-36f88d5e 5 us-east-1c in-use 2011-02-18T00:06:32+0000
246: ATTACHMENT vol-36f88d5e i-5babe737 /dev/sdf attached 2011-02-18T00:14:00+0000
247: VOLUME vol-24f88d4c 1 us-east-1c in-use 2011-02-18T00:06:21+0000
248: ATTACHMENT vol-24f88d4c i-5babe737 /dev/sdg attached 2011-02-18T00:14:10+0000
249: """]]
250:
1.16 wiki 251: ## Snapshots!
1.2 wiki 252:
1.19 wiki 253: Before we can connect to our brand new instance, we have to allow connections on SSH port (22) through the AWS EC2 firewall:
254:
255: [[!template id=programlisting text="""
256: $ ec2-authorize default -p 22
257: GROUP default
258: PERMISSION default ALLOWS tcp 22 22 FROM CIDR 0.0.0.0/0
259: """]]
260:
1.17 wiki 261: We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img*, to our instance host:
1.9 wiki 262:
263: [[!template id=programlisting text="""
264: # Upload kernel to Linux AMI
1.21 ! wiki 265: rsync -aPv -e "ssh -i $EC2_SSH_KEY" /usr/obj/sys/arch/amd64/compile/XEN3_DOMU/netbsd \
1.9 wiki 266: ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
267: # Upload disk image
268: rsync -aPv -e "ssh -i $EC2_SSH_KEY" NetBSD-AMI.img.gz \
269: ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
270: """]]
271:
1.17 wiki 272: Then, log in to the instance, via its name. We will format and mount the Grub partition, create the *menu.lst* file, then copy files to their respective partitions.
273:
274: [[!template id=programlisting text="""
275: $ ec2-describe-instances i-5babe737
276: INSTANCE i-5babe737 ami-74f0061d <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong> ip-10-99-86-193.ec2.internal running <your_ssh_key_pair_name> 0 t1.micro 2011-02-17T23:22:37+0000 us-east-1c aki-427d952b monitoring-disabled 67.202.24.108 10.99.86.193 ebs
1.9 wiki 277: $ ssh -i "$EC2_SSH_KEY" ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com
278: [...]
279: [ec2-user@ip-10-99-86-193 ~]$ sudo su
280: [root@ip-10-99-86-193 ec2-user]# mkdir /mnt/grub
281: [root@ip-10-99-86-193 ec2-user]# mkfs.ext2 /dev/sdg
282: [...]
283: [root@ip-10-99-86-193 ec2-user]# mount /dev/sdg /mnt/grub/
284: [root@ip-10-99-86-193 ec2-user]# mkdir -p /mnt/grub/boot/grub/
285: [root@ip-10-99-86-193 ec2-user]# cat > /mnt/grub/boot/grub/menu.lst << EOF
1.12 wiki 286: default=0
287: timeout=0
288: hiddenmenu
289:
290: title NetBSD AMI
291: root (hd0)
292: kernel /boot/netbsd root=xbd1
1.9 wiki 293: EOF
294: [root@ip-10-99-86-193 ec2-user]# mv netbsd /mnt/grub/boot/
295: [root@ip-10-99-86-193 ec2-user]# umount /dev/sdg
296: [root@ip-10-99-86-193 ec2-user]# gunzip < NetBSD-AMI.img.gz | dd of=/dev/sdf bs=32k
1.10 wiki 297: [root@ip-10-99-86-193 ec2-user]# sync
1.9 wiki 298: """]]
299:
1.16 wiki 300: ## Shutdown the Linux instance
1.1 wiki 301:
1.10 wiki 302: We now have to detach volumes, snapshot them, then we shutdown the Linux instance.
303:
304: [[!template id=programlisting text="""
305: # ec2-detach-volume vol-36f88d5e
306: ATTACHMENT vol-36f88d5e i-5babe737 /dev/sdf detaching 2011-02-18T00:14:00+0000
307: # ec2-detach-volume vol-24f88d4c
308: ATTACHMENT vol-24f88d4c i-5babe737 /dev/sdg detaching 2011-02-18T00:14:10+0000
309: # ec2-create-snapshot vol-36f88d5e
310: SNAPSHOT <strong>snap-deef2bb2</strong> vol-36f88d5e pending 2011-02-18T01:17:59+0000 983624114127 5
311: # ec2-create-snapshot vol-24f88d4c
312: SNAPSHOT <strong>snap-8aef2be6</strong> vol-24f88d4c pending 2011-02-18T01:18:10+0000 983624114127 1
313: # ec2-terminate-instances i-5babe737
314: INSTANCE i-5babe737 running shutting-down
315: """]]
316:
1.16 wiki 317: # Playing with your first NetBSD instance
318:
1.6 wiki 319: ## Create your first NetBSD AMI
1.1 wiki 320:
1.10 wiki 321: An AMI requires multiples components to be registered: the snapshots IDs we made in the previous chapter, as well as a specific AKI: the one that can chain-load Xenified kernels through PyGrub.
322:
1.18 wiki 323: /!\ AKIs are entitled to the same conditions as AMIs: their IDs are region-specific. So choose one carefully, or you will not be able to launch your NetBSD instance later!
1.10 wiki 324:
325: The list of AKIs that suits our situation can be obtained with the following command:
326:
327: [[!template id=programlisting text="""
328: # Obtain all kernel images (AKI) for region US East, for which manifest location contains pv-grub (for PyGrub)
329: # ec2-describe-images -a --region=us-east-1 -F image-type=kernel -F manifest-location=*pv-grub*
330: IMAGE aki-407d9529 ec2-public-images/pv-grub-hd0-V1.01-i386.gz.manifest.xml amazon available public i386 kernel instance-store paravirtual xen
1.15 wiki 331: <strong>IMAGE aki-427d952b ec2-public-images/pv-grub-hd0-V1.01-x86_64.gz.manifest.xml amazon available public x86_64 kernel instance-store paravirtual xen</strong>
1.10 wiki 332: IMAGE aki-4c7d9525 ec2-public-images/pv-grub-hd00-V1.01-i386.gz.manifest.xml amazon available public i386 kernel instance-store paravirtual xen
1.15 wiki 333: IMAGE aki-4e7d9527 ec2-public-images/pv-grub-hd00-V1.01-x86_64.gz.manifest.xml amazon available public x86_64 kernel instance-store paravirtual xen
1.10 wiki 334: """]]
335:
1.15 wiki 336: Pick the one with the correct architecture (x86_64 here). **hd0** are for AMIs where the snapshot contains no partition (where the volume is itself the whole partition), while **hd00** are for snapshots partitioned in a classical way (via MBR). Choose **hd0** AKIs. In this case, that will be **aki-427d952b**.
1.13 wiki 337:
338: We can proceed to the creation of our AMI, with:
1.10 wiki 339:
1.14 wiki 340: 1. */dev/sda1* as Grub partition (*/dev/sdg*, snapshot **snap-8aef2be6** of volume **vol-24f88d4c**)
341: 1. */dev/sda2* as root file-system (*/dev/sdf*, snapshot **snap-deef2bb2** of volume **vol-36f88d5e**)
1.10 wiki 342:
343: [[!template id=programlisting text="""
1.20 wiki 344: $ ec2-register -a x86_64 --kernel aki-427d952b --region us-east-1 \
1.10 wiki 345: -b "/dev/sda1=snap-8aef2be6" -b "/dev/sda2=snap-deef2bb2" -n "NetBSD-x86_64-current" \
346: -d "<add your own description here>
1.11 wiki 347: IMAGE <strong>ami-74d0231d</strong>
1.10 wiki 348: """]]
349:
1.16 wiki 350: ## Launch your first instance
1.1 wiki 351:
1.10 wiki 352: You can now start your own NetBSD instance, via:
353:
354: [[!template id=programlisting text="""
355: $ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c
356: RESERVATION r-08218465 983624114127 default
357: INSTANCE <strong>i-953d72f9</strong> ami-74d0231d pending 0 t1.micro 2011-02-18T02:05:46+0000 us-east-1c aki-4e7d9527 monitoring-disabled
1.11 wiki 358: *** Wait a few minutes, micro instances take time to start ***
359: # Query console output for your new instance
1.10 wiki 360: $ ec2-get-console-output i-953d72f9
1.15 wiki 361: Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
362: 2006, 2007, 2008, 2009, 2010, 2011
363: The NetBSD Foundation, Inc. All rights reserved.
364: Copyright (c) 1982, 1986, 1989, 1991, 1993
365: The Regents of the University of California. All rights reserved.
366:
367: NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011
368: jym@paris:/home/jym/cvs/obj/sys/arch/amd64/compile/XEN3_DOMU
1.10 wiki 369: [...]
370: """]]
371:
1.15 wiki 372: ## Connect to your NetBSD instance
1.1 wiki 373:
374: ## And now?
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb
![[BACK]](/icons/back.gif){kind=icon}
Return to amazon_ec2.mdwn CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [NetBSD Developer Wiki] / wikisrc