From nobody Wed Jan 21 00:28:36 2026 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 4dwlRl3PQDz6PMrK for ; Wed, 21 Jan 2026 00:28:51 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [46.21.153.22]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4dwlRk0Hlzz4LSQ; Wed, 21 Jan 2026 00:28:49 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b="WpuYA6/D"; dmarc=pass (policy=quarantine) header.from=nomadlogic.org; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 46.21.153.22 as permitted sender) smtp.mailfrom=pete@nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1768955316; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2ahyCJMjJhxKVwY3KVVBb6ck97TpvyktivQ8DS0AyNU=; b=WpuYA6/D62Mm+Kssk+FUzYY/JxEG4x5PTRl9XRTywb2T2Pg32dTGZd4CZiw+7pCMfiO6Yr rFCEOL2LYMLTsaopR6uFGVcBKAgoeVRCgPv8HOMluJ+n2Gr632mQud3bwLFAvz/Pz5pTIl qbEPY+5SkJ+n5C0yh6KeXNEegFBP1WE= Received: from topanga (47-143-52-179.fdr01.snmn.ca.ip.frontiernet.net [47.143.52.179]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 575b0f19 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 21 Jan 2026 00:28:35 +0000 (UTC) Date: Tue, 20 Jan 2026 16:28:36 -0800 From: Pete Wright To: Colin Percival Cc: "freebsd-cloud@freebsd.org" , FreeBSD Release Engineering Team Subject: Re: RFC: EC2 "pre-patched" AMIs Message-ID: References: <2b292b81-1912-4914-a4f2-cf3afc5461a3@freebsd.org> <61d82ff3-c5b1-45d0-ac55-d5bb10a30498@nomadlogic.org> <3fb002f8-55c0-4e60-9391-3ee9c8dd207e@freebsd.org> 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=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3fb002f8-55c0-4e60-9391-3ee9c8dd207e@freebsd.org> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.989]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MISSING_XM_UA(0.00)[]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:29802, ipnet:46.21.153.0/24, country:US]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MLMMJ_DEST(0.00)[freebsd-cloud@freebsd.org]; DKIM_TRACE(0.00)[nomadlogic.org:+] X-Rspamd-Queue-Id: 4dwlRk0Hlzz4LSQ On Mon, Jan 19, 2026 at 11:16:02AM -0800, Colin Percival wrote: > > > > short answer the paths seem reasonable to me, although i tend to prefer > > explicit paths rather than "/latest" just to remove all doubt as to what > > version i should expect. > > Right, I went with this plan, whereby you can launch .../latest to get the > latest version, or .../p to get that particular patchlevel. > nice! > > I am not a fan of how AWS implemented SSM, and the tooling is pretty > > awkward as well imho.  it would be super handy to have a page listing > > all of the AMI's available in an easy to parse method. > > Good idea. Which would be more useful, a single large page listing lots of > AMIs, or a search form? > i personally like the way that Alma linux did it in their wiki. having a table with the AMI's listed is easier for me, but either would be sweet. i may take a stab at automating this on my end if i end up with any cycles one of these days. -pete