Date: Mon, 2 Sep 2024 10:22:37 -0700 From: Colin Percival <cperciva@freebsd.org> To: Pete Wright <pete@nomadlogic.org>, freebsd-cloud@freebsd.org Subject: Re: New FreeBSD/EC2 AMIs: "small" flavour Message-ID: <24b38eba-428b-4484-92fe-5e33927288c8@freebsd.org> In-Reply-To: <89fab9d3-1ace-4444-aafb-cbdd9a5b0f52@nomadlogic.org> References: <f5b8dfa6-071c-41e4-8696-feb1495884ab@freebsd.org> <66e66b9b-084b-47e4-862e-98141c47a856@app.fastmail.com> <01000191afb2427e-8bb3eb6e-81f7-48a9-bc10-d7e4e8865dd2-000000@email.amazonses.com> <6d44f095-d137-456f-8194-e3430647810f@app.fastmail.com> <e22eabe7-f852-42ac-9ac4-048302163d4d@freebsd.org> <89fab9d3-1ace-4444-aafb-cbdd9a5b0f52@nomadlogic.org>
index | next in thread | previous in thread | raw e-mail
On 9/2/24 08:19, Pete Wright wrote: > this seems like a good idea from my POV as an admin. Although I think it may > be helpful to keep the AWS CLI install on boot step in some use-cases. My > general workflow is to use packer to build a site specific AMI where I install > our specific configs and run freebsd-update then disable it on subsequent > boots. My goal in those scenarios is to improve first-boot time for > auto-scaling. > > When I do use "vanilla" AMI's its usually for a research/testing/debugging > task so having the awscli get installed on firstboot would save me some hassle > of having to do that by hand. It's certainly not a deal breaker though, just > my two bits. The "small" AMIs still have firstboot-pkgs installed, so you can launch the image with a user-data file of >>/etc/rc.conf firstboot_pkgs_list="devel/py-awscli" and it will install that package for you. I just figured that if people wanted "small" then it made sense to change the default. -- Colin Percival FreeBSD Release Engineering Lead & EC2 platform maintainer Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoidhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24b38eba-428b-4484-92fe-5e33927288c8>
