From owner-freebsd-cloud@freebsd.org  Mon Jan  1 23:54:05 2018
Return-Path: <owner-freebsd-cloud@freebsd.org>
Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E935DEA321B
 for <freebsd-cloud@mailman.ysv.freebsd.org>;
 Mon,  1 Jan 2018 23:54:05 +0000 (UTC) (envelope-from raf@rafal.net)
Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C107F63C8E
 for <freebsd-cloud@freebsd.org>; Mon,  1 Jan 2018 23:54:05 +0000 (UTC)
 (envelope-from raf@rafal.net)
Received: from [192.168.40.23]
 (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by smtp.mxes.net (Postfix) with ESMTPSA id 9F1F62754C;
 Mon,  1 Jan 2018 18:54:02 -0500 (EST)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: AMI building AMI
From: Rafal Lukawiecki <raf@rafal.net>
X-Mailer: iPad Mail (15C153)
In-Reply-To: <01000160b3e11756-1d74d2fc-6486-4458-87cd-b88203a99a77-000000@email.amazonses.com>
Date: Mon, 1 Jan 2018 23:54:01 +0000
Cc: freebsd-cloud@freebsd.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F125915-3331-4F00-97E4-B6763DFCEBA4@rafal.net>
References: <085D225B-2E99-4540-B693-223087B14A27@rafal.net>
 <0100016099578ea7-02da1d5c-997d-47be-9cd8-dc6b75bbeda6-000000@email.amazonses.com>
 <8BCB67B8-DE56-491A-8E6A-95AFB83F71D6@rafal.net>
 <0100016099671dff-32d986bf-3979-40a3-accf-4d17c2020403-000000@email.amazonses.com>
 <8538BFB9-B82C-4520-ADB3-E25040EA1B30@rafal.net>
 <01000160a0283ad5-12b330d3-3f4b-43ea-9cdc-2524f5f42f4a-000000@email.amazonses.com>
 <0C1308D4-AFD6-4216-83A6-4687157EC8D3@rafal.net>
 <A4886392-18D5-44CF-BFEA-A802AF4F850E@rafal.net>
 <01000160b3e11756-1d74d2fc-6486-4458-87cd-b88203a99a77-000000@email.amazonses.com>
To: Colin Percival <cperciva@tarsnap.com>
X-BeenThere: freebsd-cloud@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure,
 etc.\)" <freebsd-cloud.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-cloud>,
 <mailto:freebsd-cloud-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-cloud/>
List-Post: <mailto:freebsd-cloud@freebsd.org>
List-Help: <mailto:freebsd-cloud-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-cloud>,
 <mailto:freebsd-cloud-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jan 2018 23:54:06 -0000


> On 1 Jan 2018, at 22:39, Colin Percival <cperciva@tarsnap.com> wrote:
>=20
> Maybe a dumb question, but do you really need to use a configinit script
> for this?  I know I showed that as an example in my blog post, but I
> expected that the main way the AMI builder would be used would be by
> SSHing in and setting things up "manually".

Automation is attractive but not not a primary goal this time. Being able to=
 kick it off from an EC2 launch template and come back to a finished AMI, ma=
kes it more likely I=E2=80=99d have it done the next few times the AMI needs=
 remaking.

I suppose I will need to do it manually the first time to see where the issu=
es are. I will share the feedback with you in case it is useful for a future=
 post.

Many thanks,
Rafal=