From nobody Mon Mar 6 14:08:51 2023 X-Original-To: freebsd-cloud@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PVgRc474xz3wwx0 for ; Mon, 6 Mar 2023 14:09:00 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4PVgRc3WqLz3QPh; Mon, 6 Mar 2023 14:09:00 +0000 (UTC) (envelope-from meta@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1678111740; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nsZEQVTjaZ4VD3FMO4Z2C19mPUsffqHHMt/Xq65xBAg=; b=Z2TzgzRP+k3kRVzhxHjeN5DFU1tRG2K6T9I9REfJEpYcrlE9F7DMuhfJgeE83A46A6bg6V qIP5FemROgT2Y8l1qyMNIisBL0kIyDeDqMgyImD9Cpj1oz5jNJMeZJdf+1JwogFZna0WIN rbdbMZRm57om4qCDhEX4APwOoPlf5q9t9IM5CMOvntjIDnzAe4i5JHaD3I4E0ci2WR64Se nuVSI/lIr9xeQ9XsUalZKQFmwQ4EwwThwsYjZPbxErtm/JgFA51JKAP7EFs0Rx9qcEUfff aAixFJqbHp5M7ats6i5xVsbzfXOasjZ1zWjmWUiFLCrdkl4phgWJhlRk+pbGRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1678111740; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nsZEQVTjaZ4VD3FMO4Z2C19mPUsffqHHMt/Xq65xBAg=; b=gwKb6OCCf70898A0Ecvr9SbQ83AJQenbqS25LOU+AgFlpE1Iwkr7203d9+c+up06+Ue7F4 ZQvRs7BJwuvYrF5vFMdCI5JSyrwilvuVzNmrB8fVKMkg4ldowjWundQgO0UidEMadFIQAI NDQnXV7M7WMBC4A9HRiz800oVO1UXnC12Ew59V4skBkAiJXHZjmGR4uveDgq6RfEtHUI+u jtZy/v4d/+5Gzg+uqbY6ukOWqpd2vemgwVbHAq/O+HRD65CVBDySOf0wcJ6PjZg1RPwH82 Mu2LKVPQm8jqawsXBam/mRb/CsPCdQJrDmT5JT9Fw2HqLwm9ztsr35tTGHel+g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1678111740; a=rsa-sha256; cv=none; b=HhDF7jIzHAU9J4W1/X5LivkIrOmGgCkwC8S1jxLgK8lwlf9IzRSgyAmeycY3Gr6PG0x5Pq 69XblVnWLKvSr983tHtqKhx0T5KgWY2I5DAWXYJhhu7nldKCcjiwumLwyBTzRkKAQth1dM rLp+gl7NaRAsL7HrEc4hx/2dlhcuOxLak0GZT5Y0aRyQVJ/8grrLtYMRH7Z/aUD+mHbmLb 3VSmHq7PfiWVbD0V2aDVfzmktNmW5mvHRl321yIVqC0dfQuX08AvKVI/6NiykSYjayY7j0 JKaOnBNKREgin7z3zoPbtsphnQlv8B/BcoMcA6k/G0z/foK6jzn/kfncLx9G0g== Received: from icepick.vmeta.jp (unknown [IPv6:2403:bd80:c100:411:e10f:5f62:d735:93a1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: meta/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4PVgRb2McZz16WN; Mon, 6 Mar 2023 14:08:59 +0000 (UTC) (envelope-from meta@FreeBSD.org) Date: Mon, 6 Mar 2023 23:08:51 +0900 From: Koichiro Iwao To: Colin Percival Cc: freebsd-cloud@FreeBSD.org Subject: Re: How are official EC2 images built? Message-ID: <20230306140851.hduau66beidb7rne@icepick.vmeta.jp> X-Operating-System: FreeBSD 13.2-STABLE amd64 References: <20230306021533.ght5ouvxg6zrihfr@icepick.vmeta.jp> <01000186b5b4a976-9499f902-9004-4929-a9b3-6d6db764dc76-000000@email.amazonses.com> List-Id: FreeBSD on cloud platforms (EC2, GCE, Azure, etc.) List-Archive: https://lists.freebsd.org/archives/freebsd-cloud List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-cloud@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <01000186b5b4a976-9499f902-9004-4929-a9b3-6d6db764dc76-000000@email.amazonses.com> X-ThisMailContainsUnwantedMimeParts: N On Mon, Mar 06, 2023 at 06:56:01AM +0000, Colin Percival wrote: > On 3/5/23 18:15, Koichiro Iwao wrote: > > Does anyone how offical EC2 images [1] are built? > > They are built using the `make ec2ami` target in the src/release directory. > That target builds a disk image and then converts it into an AMI using the > bsdec2-image-upload utility (available in the ports tree). > > > I mean if the build script is public. I would like to create private > > custom images with some customization based on official image. > > I wrote about some of the options a few years ago: > https://www.daemonology.net/blog/2018-12-26-the-many-ways-to-launch-FreeBSD-in-EC2.html > > I'm guessing the AMI Builder option will best suit your need for "some > customization" but if you need to make changes to the base system then > you'll > want to use `make ec2ami`. Thanks, what I actually wanted to create is a qcow2 image with cloud-init/firstboot enabled to be run by vm-bhyve, removing EC2-specific stuffs from official EC2 images. I'll try to make EC2 images next. Anyway, it helps a lot. Thanks! -- meta