File:  [NetBSD Developer Wiki] / wikisrc / amazon_ec2.mdwn
Revision 1.23: download - view: text, annotated - select for diffs
Sat Feb 19 04:34:56 2011 UTC (7 years, 9 months ago) by wiki
Branches: MAIN
CVS tags: HEAD
web commit by jym: Last words. Need one last thing: pre-made AMIs for each region. I will build them next week.

    1: [[!toc]]
    2: 
    3: # Introduction
    4: 
    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.
    6: 
    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.
   10: 
   11: ## Quick overview
   12: 
   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:
   14: 
   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.
   17: 
   18: ## What do you need to know?
   19: 
   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.
   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.
   28: 
   29: ### Keep your credentials!
   30: 
   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: 
   33: For convenience, you could store them under a *.ec2* directory inside your *$HOME*:
   34: 
   35: [[!template id=programlisting text="""
   36: $ ls .ec2/                                                                
   37: cert-SOMERANDOMKEY.pem # the X.509 certificate
   38: id_rsa.ec2             # private RSA SSH key
   39: id_rsa.ec2.pub         # public RSA SSH key
   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
   49: export EC2_SSH_KEYNAME=<your_ssh_key_pair_name>
   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: 
   57: ## Installing EC2 API tools
   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: 
   68: ## EC2 vocabulary -- last notes
   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.
   75: 
   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: 
   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.
   79: 
   80: # Using pre-made AMIs
   81: 
   82: XXX TODO
   83: 
   84: # Build-up your NetBSD system
   85: 
   86: ## Fetch and build NetBSD
   87: 
   88: 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.
   89: 
   90: This tutorial assumes that you will build the system under */mnt/ec2*.
   91: 
   92: /!\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.
   93: 
   94: [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*:
   95: 
   96: [[!template id=programlisting text="""
   97: cd /usr/
   98: # grab a recent src.tgz file (use curl(1), ftp(1), wget(1), ...)
   99: ftp -a 'http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/src.tar.gz'
  100: # Decompress
  101: tar -xzpf src.tar.gz
  102: cd src
  103: # build distribution and kernel
  104: ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -m amd64 -U distribution
  105: ./build.sh -O ../obj -T ../tools -m amd64 kernel=XEN3_DOMU
  106: # install distribution in /mnt/ec2
  107: ./build.sh -O ../obj -T ../tools -D ../dest -R ../release -U install=/mnt/ec2
  108: """]]
  109: 
  110: # Configuration of your NetBSD EC2 tree
  111: 
  112: /!\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.
  113: 
  114: Under */mnt/ec2*, edit the files to add (or modify) these lines:
  115: 
  116: [[!template id=filecontent name=etc/rc.conf text="""
  117: rc_configured=YES
  118: 
  119: sshd=YES # for remote shell access to instance
  120: """]]
  121: 
  122: [[!template id=filecontent name=etc/ssh/sshd_config text="""
  123: # Allows root to login via authentication keys
  124: PermitRootLogin without-password
  125: """]]
  126: 
  127: This file is needed if you want to login via the EC2 SSH key pair created previously:
  128: 
  129: [[!template id=filecontent name=etc/rc.d/ec2-init text="""
  130: #!/bin/sh
  131: #
  132: # PROVIDE: amazon-ec2
  133: # REQUIRE: NETWORKING
  134: # BEFORE:  LOGIN
  135: 
  136: $_rc_subr_loaded . /etc/rc.subr
  137: 
  138: name="ec2_init"
  139: start_cmd="ec2_init"
  140: stop_cmd=":"
  141: 
  142: METADATA_URL="http://169.254.169.254/latest/meta-data/"
  143: SSH_KEY_URL="public-keys/0/openssh-key"
  144: HOSTNAME_URL="hostname"
  145: 
  146: SSH_KEY_FILE="/root/.ssh/authorized_keys"
  147: 
  148: ec2_init()
  149: {
  150:         (
  151:         umask 022
  152:         # fetch the key pair from Amazon Web Services
  153:         EC2_SSH_KEY=$(ftp -o - "${METADATA_URL}${SSH_KEY_URL}")
  154: 
  155:         if [ -n "$EC2_SSH_KEY" ]; then
  156:                 # A key pair is associated with this instance, add it
  157:                 # to root 'authorized_keys' file
  158:                 mkdir -p $(dirname "$SSH_KEY_FILE")
  159:                 touch "$SSH_KEY_FILE"
  160:                 cd $(dirname "$SSH_KEY_FILE")
  161: 
  162:                 grep -q "$EC2_SSH_KEY" "$SSH_KEY_FILE"
  163:                 if [ $? -ne 0 ]; then
  164:                         echo "Setting EC2 SSH key pair: ${EC2_SSH_KEY##* }"
  165:                         echo "$EC2_SSH_KEY" >> "$SSH_KEY_FILE"
  166:                 fi
  167:         fi
  168: 
  169:         # set hostname
  170:         HOSTNAME=$(ftp -o - "${METADATA_URL}${HOSTNAME_URL}")
  171:         echo "Setting EC2 hostname: ${HOSTNAME}"
  172:         echo "$HOSTNAME" > /etc/myname
  173:         hostname "$HOSTNAME"
  174:         )
  175: }
  176: 
  177: 
  178: load_rc_config $name
  179: run_rc_command "$1"
  180: """]]
  181: 
  182: Create various files and directories:
  183: 
  184: [[!template id=programlisting text="""
  185: cd /mnt/ec2
  186: # Add proc and kern directories
  187: mkdir grub kern proc
  188: # EC2 network configuration, via DHCP
  189: echo "dhcp" > etc/ifconfig.xennet0
  190: # Basic fstab entries
  191: cat > etc/fstab << EOF
  192: /dev/xbd1a /        ffs    rw 1 1
  193: /dev/xbd0a /grub    ext2fs rw 2 2
  194: kernfs     /kern    kernfs rw
  195: ptyfs      /dev/pts ptyfs  rw
  196: procfs     /proc    procfs rw
  197: EOF
  198: # EC2 startup script (if you installed it)
  199: if [ -f etc/rc.d/ec2-init ]; then
  200:     chmod 755 etc/rc.d/ec2-init
  201: fi
  202: """]]
  203: 
  204: 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):
  205: 
  206: [[!template id=programlisting text="""
  207: $ makefs -t ffs -B le -s 256m -N /mnt/ec2/etc/ -o density=32k NetBSD-AMI.img /mnt/ec2/ 
  208: Calculated size of `NetBSD-AMI.img': 268435456 bytes, 7345 inodes
  209: Extent size set to 8192
  210: NetBSD-AMI.img: 256.0MB (524288 sectors) block size 8192, fragment size 1024
  211:         using 5 cylinder groups of 53.88MB, 6896 blks, 1728 inodes.
  212: super-block backups (for fsck -b #) at:
  213:      32, 110368, 220704, 331040, 441376,
  214: Populating `NetBSD-AMI.img'
  215: Image `NetBSD-AMI.img' complete
  216: $ gzip -9n NetBSD-AMI.img
  217: """]]
  218: 
  219: # Upload NetBSD to EC2
  220: 
  221: 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.
  222: 
  223: 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.
  224: 
  225: 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.
  226: 
  227: ## Create an Amazon Linux instance
  228: 
  229: 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.
  230: 
  231: [[!template id=programlisting text="""
  232: $ ec2-run-instances ami-74f0061d -t t1.micro -z us-east-1c -k $EC2_SSH_KEYNAME
  233: RESERVATION     r-1ab61377      983624114127    default
  234: INSTANCE        <strong>i-5babe737</strong>      ami-74f0061d                    pending &lt;your_ssh_key_pair_name&gt;  0               t1.micro        2011-02-17T23:15:04+0000        us-east-1c      aki-427d952b                    monitoring-disabled                                     ebs                                     paravirtual     xen     
  235: """]]
  236: 
  237: Use the instance identifier **i-XXXXXXX** to query the instance state via **ec2-describe-instances**. It will take some time to launch:
  238: 
  239: [[!template id=programlisting text="""
  240: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
  241: $ sleep 5 && ec2-describe-instances i-5babe737 | grep running
  242: INSTANCE        i-5babe737      ami-74f0061d    <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong>       ip-10-99-86-193.ec2.internal    running &lt;your_ssh_key_pair_name&gt;  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
  243: """]]
  244: 
  245: ## Create and attach your NetBSD volumes
  246: 
  247: We will have to create and attach two EBS volumes:
  248: 
  249: 1. one to contain the Grub *menu.lst* config file, as well as the NetBSD kernel.
  250: 1. the other one will contain the root file-system.
  251: 
  252: [[!template id=programlisting text="""
  253: <strong>ec2-create-volume -s 1 -z us-east-1c</strong> # 1GiB -- will be used for Grub and kernel
  254: VOLUME  vol-24f88d4c    1               us-east-1c      creating        2011-02-18T00:06:21+0000
  255: <strong>ec2-create-volume -s 5 -z us-east-1c</strong> # 5GiB -- will contain the root file-system
  256: VOLUME  vol-36f88d5e    5               us-east-1c      creating        2011-02-18T00:06:32+0000
  257: *** Wait until both volumes are marked as "available" ***
  258: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
  259: VOLUME  vol-36f88d5e    5               us-east-1c      available       2011-02-18T00:06:32+0000
  260: VOLUME  vol-24f88d4c    1               us-east-1c      available       2011-02-18T00:06:21+0000
  261: # Attach them under /dev/sdf and /dev/sdg respectively
  262: <strong>ec2-attach-volume vol-36f88d5e -i i-5babe737 -d "/dev/sdf"</strong> # root file-system
  263: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        attaching       2011-02-18T00:13:53+0000
  264: <strong>ec2-attach-volume vol-24f88d4c -i i-5babe737 -d "/dev/sdg"</strong> # Grub and kernel
  265: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        attaching       2011-02-18T00:14:02+0000
  266: *** Wait until both volumes are "attached" ***
  267: <strong>ec2-describe-volumes vol-24f88d4c vol-36f88d5e</strong>
  268: VOLUME  vol-36f88d5e    5               us-east-1c      in-use  2011-02-18T00:06:32+0000
  269: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        attached        2011-02-18T00:14:00+0000
  270: VOLUME  vol-24f88d4c    1               us-east-1c      in-use  2011-02-18T00:06:21+0000
  271: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        attached        2011-02-18T00:14:10+0000
  272: """]]
  273: 
  274: ## Snapshots!
  275: 
  276: Before we can connect to our brand new instance, we have to allow connections on SSH port (22) through the AWS EC2 firewall:
  277: 
  278: [[!template id=programlisting text="""
  279: $ ec2-authorize default -p 22
  280: GROUP           default 
  281: PERMISSION              default ALLOWS  tcp     22      22      FROM    CIDR    0.0.0.0/0
  282: """]]
  283: 
  284: We can now upload the kernel and the NetBSD disk image created earlier, *NetBSD-AMI.img*, to our instance host:
  285: 
  286: [[!template id=programlisting text="""
  287: # Upload kernel to Linux AMI
  288: rsync -aPv -e "ssh -i $EC2_SSH_KEY" /usr/obj/sys/arch/amd64/compile/XEN3_DOMU/netbsd \
  289:         ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
  290: # Upload disk image
  291: rsync -aPv -e "ssh -i $EC2_SSH_KEY" NetBSD-AMI.img.gz \
  292:         ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com:
  293: """]]
  294: 
  295: 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.
  296: 
  297: [[!template id=programlisting text="""
  298: $ ec2-describe-instances i-5babe737
  299: INSTANCE        i-5babe737      ami-74f0061d    <strong>ec2-67-202-24-108.compute-1.amazonaws.com</strong>       ip-10-99-86-193.ec2.internal    running &lt;your_ssh_key_pair_name&gt;  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
  300: $ ssh -i "$EC2_SSH_KEY" ec2-user@ec2-67-202-24-108.compute-1.amazonaws.com
  301: [...]
  302: [ec2-user@ip-10-99-86-193 ~]$ sudo su
  303: [root@ip-10-99-86-193 ec2-user]# mkdir /mnt/grub
  304: [root@ip-10-99-86-193 ec2-user]# mkfs.ext2 /dev/sdg
  305: [...]
  306: [root@ip-10-99-86-193 ec2-user]# mount /dev/sdg /mnt/grub/
  307: [root@ip-10-99-86-193 ec2-user]# mkdir -p /mnt/grub/boot/grub/
  308: [root@ip-10-99-86-193 ec2-user]# cat > /mnt/grub/boot/grub/menu.lst << EOF
  309: default=0
  310: timeout=0
  311: hiddenmenu
  312: 
  313: title NetBSD AMI
  314: root (hd0)
  315: kernel /boot/netbsd root=xbd1
  316: EOF
  317: [root@ip-10-99-86-193 ec2-user]# mv netbsd /mnt/grub/boot/
  318: [root@ip-10-99-86-193 ec2-user]# umount /dev/sdg
  319: [root@ip-10-99-86-193 ec2-user]# gunzip < NetBSD-AMI.img.gz | dd of=/dev/sdf bs=32k
  320: [root@ip-10-99-86-193 ec2-user]# sync
  321: """]]
  322: 
  323: ## Shutdown the Linux instance
  324: 
  325: We now have to detach volumes, snapshot them, then we shutdown the Linux instance.
  326: 
  327: [[!template id=programlisting text="""
  328: # ec2-detach-volume vol-36f88d5e
  329: ATTACHMENT      vol-36f88d5e    i-5babe737      /dev/sdf        detaching       2011-02-18T00:14:00+0000
  330: # ec2-detach-volume vol-24f88d4c
  331: ATTACHMENT      vol-24f88d4c    i-5babe737      /dev/sdg        detaching       2011-02-18T00:14:10+0000
  332: # ec2-create-snapshot vol-36f88d5e
  333: SNAPSHOT        <strong>snap-deef2bb2</strong>   vol-36f88d5e    pending 2011-02-18T01:17:59+0000                983624114127    5
  334: # ec2-create-snapshot vol-24f88d4c
  335: SNAPSHOT        <strong>snap-8aef2be6</strong>   vol-24f88d4c    pending 2011-02-18T01:18:10+0000                983624114127    1
  336: # ec2-terminate-instances i-5babe737
  337: INSTANCE        i-5babe737      running shutting-down
  338: """]]
  339: 
  340: # Playing with your first NetBSD instance
  341: 
  342: ## Create your first NetBSD AMI
  343: 
  344: 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.
  345: 
  346: /!\ 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!
  347: 
  348: The list of AKIs that suits our situation can be obtained with the following command:
  349: 
  350: [[!template id=programlisting text="""
  351: # Obtain all kernel images (AKI) for region US East, for which manifest location contains pv-grub (for PyGrub)
  352: # ec2-describe-images -a --region=us-east-1 -F image-type=kernel -F manifest-location=*pv-grub*
  353: IMAGE   aki-407d9529    ec2-public-images/pv-grub-hd0-V1.01-i386.gz.manifest.xml        amazon  available       public          i386    kernel                          instance-store  paravirtual     xen
  354: <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>
  355: IMAGE   aki-4c7d9525    ec2-public-images/pv-grub-hd00-V1.01-i386.gz.manifest.xml       amazon  available       public          i386    kernel                          instance-store  paravirtual     xen
  356: 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
  357: """]]
  358: 
  359: 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**.
  360: 
  361: We can proceed to the creation of our AMI, with:
  362: 
  363: 1. */dev/sda1* as Grub partition (*/dev/sdg*, snapshot **snap-8aef2be6** of volume **vol-24f88d4c**)
  364: 1. */dev/sda2* as root file-system (*/dev/sdf*, snapshot **snap-deef2bb2** of volume **vol-36f88d5e**)
  365: 
  366: [[!template id=programlisting text="""
  367: $ ec2-register -a x86_64 --kernel aki-427d952b --region us-east-1 \
  368:     -b "/dev/sda1=snap-8aef2be6" -b "/dev/sda2=snap-deef2bb2" -n "NetBSD-x86_64-current" \
  369:     -d "&lt;add your own description here&gt;
  370: IMAGE   <strong>ami-74d0231d</strong>
  371: """]]
  372: 
  373: ## Launch your first instance
  374: 
  375: You can now start your own NetBSD instance, via:
  376: 
  377: [[!template id=programlisting text="""
  378: $ ec2-run-instances ami-74d0231d -t t1.micro -z us-east-1c     
  379: RESERVATION     r-08218465      983624114127    default
  380: INSTANCE        <strong>i-953d72f9</strong>      ami-74d0231d                    pending         0               t1.micro        2011-02-18T02:05:46+0000        us-east-1c      aki-4e7d9527                    monitoring-disabled
  381: *** Wait a few minutes, micro instances take time to start ***
  382: # Query console output for your new instance
  383: $ ec2-get-console-output i-953d72f9
  384: Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
  385:     2006, 2007, 2008, 2009, 2010, 2011
  386:     The NetBSD Foundation, Inc.  All rights reserved.
  387: Copyright (c) 1982, 1986, 1989, 1991, 1993
  388:     The Regents of the University of California.  All rights reserved.
  389: 
  390: NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011
  391: [...]
  392: NetBSD/amd64 (ip-10-112-58-223.ec2.internal) (console)
  393: 
  394: login: 
  395: """]]
  396: 
  397: ## Connect to your NetBSD instance
  398: 
  399: Connection is similar to the one you used for the Amazon Linux instance, except that you login as "root" instead of "ec2-user":
  400: 
  401: [[!template id=programlisting text="""
  402: $ ec2-describe-instances i-953d72f9
  403: RESERVATION     r-da8021b7      983624114127    default
  404: INSTANCE        i-953d72f9      ami-74d0231d    <strong>ec2-50-16-3-55.compute-1.amazonaws.com</strong>  ip-10-112-58-223.ec2.internal   running &lt;your_ssh_key_pair_name&gt;  0               t1.micro        2011-02-19T04:01:03+0000        us-east-1c      aki-427d952b                    monitoring-disabled     50.16.3.55      10.112.58.223                   ebs                                     paravirtual     xen     
  405: BLOCKDEVICE     /dev/sda1       vol-ec3c4a84    2011-02-19T04:01:31.000Z        
  406: BLOCKDEVICE     /dev/sda2       vol-ee3c4a86    2011-02-19T04:01:31.000Z        
  407: $ ssh -i "$EC2_SSH_KEY" root@ec2-50-16-3-55.compute-1.amazonaws.com
  408: The authenticity of host 'ec2-50-16-3-55.compute-1.amazonaws.com (50.16.3.55)' can't be established.
  409: [...]
  410: Thank you for helping us test and improve NetBSD.
  411: 
  412: Terminal type is xterm.
  413: We recommend that you create a non-root account and use su(1) for root access.
  414: ip-10-112-58-223# uname -a
  415: NetBSD ip-10-112-58-223.ec2.internal 5.99.45 NetBSD 5.99.45 (XEN3_DOMU) #9: Wed Feb 16 21:14:49 CET 2011  jym@paris:/home/jym/cvs/obj/sys/arch/amd64/compile/XEN3_DOMU amd64
  416: ip-10-112-58-223# 
  417: """]]
  418: 
  419: Done!
  420: 
  421: ## And now?
  422: 
  423: Well, you got a NetBSD instance that is in almost every part similar to what a NetBSD domU can be. You can use this domU to host Internet services, run a database, extend your build farm, or use it as a sandbox. The AMI being built around snapshots, you can play and break your instance in every way you want; just restart one anew if you need to. Don't forget that Amazon will charge acccordingly :)
  424: 
  425: Remember, you can query information regarding your AWS account through [[!template id=pkg category=misc name=ec2-api-tools]] package. It is quite easy to use these tools for scripting; for a more elaborate, graphical interface, use the [Amazon Management Console](https://console.aws.amazon.com/ec2/home).

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb