Date: Sun, 05 Mar 2023 18:30:40 -0800 From: "Pat Maddox" <pat@patmaddox.com> To: freebsd-cloud@freebsd.org Subject: Re: How are official EC2 images built? Message-ID: <dff102d7-b46c-41db-ac82-676ffba0c485@app.fastmail.com> In-Reply-To: <20230306021533.ght5ouvxg6zrihfr@icepick.vmeta.jp> References: <20230306021533.ght5ouvxg6zrihfr@icepick.vmeta.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
https://cgit.freebsd.org/src/tree/release/Makefile.ec2 https://cgit.freebsd.org/src/tree/release/tools/ec2.conf I have opted to build images a bit differently, not using the stuff in s= rc/release. I=E2=80=99ve done two approaches. The first is to attach a second disk to an EC2 instance, install FreeBSD= onto it with customizations, and then image the disk (https://gist.gith= ub.com/patmaddox/9f20edcb50ff15fa9edd1d4e38d07e50). The way I=E2=80=99m doing it now is to use poudriere to make an img file= , and then upload that image to S3, snapshot it (aws ec2 import-snapshot= =E2=80=93disk-container Format=3Draw,Url=3Ds3://mybucket/myimage.img) a= nd finally make an AMI from that snapshot. The stuff in src/release is good for knowing what changes to make to con= fig files, or packages to install. Pat On Sun, Mar 5, 2023, at 6:15 PM, Koichiro Iwao wrote: > Hi,=20 > > Does anyone how offical EC2 images [1] are built? > I mean if the build script is public. I would like to create private > custom images with some customization based on official image. > > [1]=20 > https://aws.amazon.com/marketplace/seller-profile?id=3D92bb514d-02bc-4= 9fd-9727-c474863f63da&ref=3Ddtl_prodview-ukzmy5dzc6nbq > > --=20 > meta <meta@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dff102d7-b46c-41db-ac82-676ffba0c485>