From nobody Wed Jan 21 01:47:44 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 4dwnBw1Dwsz6PSXt for ; Wed, 21 Jan 2026 01:47:52 +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 4dwnBv3Lt9z3C48; Wed, 21 Jan 2026 01:47:51 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1768960063; 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=q6t3hY+i2Z464mcp70G8RLhg05rYYE43XfQn0bs25B4=; b=2fFzcc/Akt8sbUnVFQi/kJEPLrG/YBDWHXGMW9JpYH6iqvGASledWKp/+mu+LhM4Sr3eTJ KLctvKw/TbN/UuAf6l0vtksEMirrNm/0lvKKSHx3FXdIfEn6vKN/Oa4phl90jKhoTetnCM uUQDP/Ke5yX7chrrGOFVytQaxCGctnw= Received: from [192.168.1.182] (47-143-52-179.fdr01.snmn.ca.ip.frontiernet.net [47.143.52.179]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 61e6308e (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 21 Jan 2026 01:47:42 +0000 (UTC) Message-ID: Date: Tue, 20 Jan 2026 17:47:44 -0800 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 User-Agent: Mozilla Thunderbird Subject: Re: RFC: EC2 "pre-patched" AMIs To: Colin Percival Cc: "freebsd-cloud@freebsd.org" , FreeBSD Release Engineering Team References: <2b292b81-1912-4914-a4f2-cf3afc5461a3@freebsd.org> <61d82ff3-c5b1-45d0-ac55-d5bb10a30498@nomadlogic.org> <3fb002f8-55c0-4e60-9391-3ee9c8dd207e@freebsd.org> <8372af52-7d99-4e55-819a-79b48aa2722f@freebsd.org> Content-Language: en-US From: Pete Wright In-Reply-To: <8372af52-7d99-4e55-819a-79b48aa2722f@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:46.21.153.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dwnBv3Lt9z3C48 On 1/20/26 16:59, Colin Percival wrote: > On 1/20/26 16:28, Pete Wright wrote: >> On Mon, Jan 19, 2026 at 11:16:02AM -0800, Colin Percival wrote: >>>> 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. > > Hmm, Alma Linux has far fewer images than us... for each release, they have > an amd64 image and an arm64 image, while we have 16 (ufs vs zfs filesystem, > and "base", "small", "cloud-init" and "builder" flavours).  That's 480 AMIs > we provide for each release, or possibly more if Amazon added more regions > while I wasn't paying attention. > > So it might make for a very large table, but it's certainly doable.  I > don't > think a wiki is a good place for this though, just from the perspective of > wanting to make sure that nobody tampers with the list of AMIs. > oh right that's a great point, in light of that a wiki page or webpage even wouldn't be very helpful. i guess one could create a csv or JSON document for easy parsing...but at the end of the day it's probably better to create a wrapper around the appropriate AWS command, or to just memorize the incantation. i don't know if its just me but this syntax has always felt awkward despite its power: aws --region us-west-2 ssm get-parameters-by-path --path /aws/service/freebsd/amd64/base/ufs/15.0/ or aws --region us-west-2 ssm get-parameters --name /aws/service/freebsd/amd64/base/ufs/15.0/RELEASE --query 'Parameters[].Value' i will say though after playing with this some more your suggested changes definitely make sense to me. -pete -- Pete Wright pete@nomadlogic.org