Date: Tue, 20 Jan 2026 16:28:36 -0800 From: Pete Wright <pete@nomadlogic.org> To: Colin Percival <cperciva@freebsd.org> Cc: "freebsd-cloud@freebsd.org" <freebsd-cloud@freebsd.org>, FreeBSD Release Engineering Team <re@FreeBSD.org> Subject: Re: RFC: EC2 "pre-patched" AMIs Message-ID: <aXAdNudYV32_NW2Z@topanga> In-Reply-To: <3fb002f8-55c0-4e60-9391-3ee9c8dd207e@freebsd.org> References: <2b292b81-1912-4914-a4f2-cf3afc5461a3@freebsd.org> <61d82ff3-c5b1-45d0-ac55-d5bb10a30498@nomadlogic.org> <3fb002f8-55c0-4e60-9391-3ee9c8dd207e@freebsd.org>
index | next in thread | previous in thread | raw e-mail
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<number> 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. -petehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aXAdNudYV32_NW2Z>