Why bother with any of this. You should build your own images and this is exactly what Image Builder does using lorax/andconda. You can use the same templates to create consistent images across AWS, GCP, Azure and more.

For AWS you might need a couple of RPMs - ec2-utils and ec2-net-utils and maybe another if you want to use instance connect. Just get the src RPMs from an Amazon Linux 2 image, rebuild the RPMS for CentOS8. You don't even need to do any blueprint configs just modify the kickstart templates and you are good to go.

Here's one I put together for a base AMI. Idiomatic and much cleaner that packer. You can build both arm64 and x86_64.

https://gist.github.com/ak2196/53ee89c039f41b3701ba04e89aa72068

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_a_customized_rhel_system_image/composer-description_composing-a-customized-rhel-system-image

On Sun, May 24, 2020 at 9:50 AM Alan Ivey <alanivey@gmail.com> wrote:
I have Packer and shell scripts for using the official RHEL8 AMIs for x86_64 and aarch64 to create minimal (with a couple of AWS-specific tools; search "optional" in the shell script) CentOS 8 AMIs. Hopefully this is helpful to others: https://gist.github.com/alanivey/68712e6172b793037fbd77ebb3112c3f

On Sun, May 17, 2020 at 4:41 AM Nico Kadel-Garcia <nkadel@gmail.com> wrote:
On Sat, May 16, 2020 at 11:58 PM Thomas Stephen Lee <lee.iitb@gmail.com> wrote:
>
> On Sun, May 17, 2020 at 4:35 AM Nico Kadel-Garcia <nkadel@gmail.com> wrote:
>>
>> On Sat, May 16, 2020 at 11:07 AM Fabian Arrotin <arrfab@centos.org> wrote:
>> >
>> > On 16/05/2020 16:20, Thomas Stephen Lee wrote:
>> > > Hi,
>> > >
>> > > I am a user of CentOS 8.
>> > > When can we expect an image on AWS?
>> > > I am just learning AWS and would like to use CentOS 8 for that.
>> > >
>> > > https://wiki.centos.org/SpecialInterestGroup/CloudInstance
>> > >
>> > > says that this is the list to ask.
>> > >
>> > > thanks
>> > >
>> > > ---
>> > > Lee
>> > >
>> >
>> > we built CentOS 8 AMI for both x86_64 and aarch64 and I was able to
>> > import these images in our own account, and could boot these images fine.
>> > We tried to reach out to AWS multiple times but no answer so actually
>> > I'd be tempted to just share for 8.2.2004 release the AMIs and announce
>> > that nobody can use marketplace but can directly launched shared AMIs
>> > when the have the reference , so like what Fedora is doing (we never
>> > were able to get the 8.0.1905 nor 8.1911 images published on
>> > marketplace) :-(
>>
>> I've done it by hand now, for CentOS 8 and RHEL 8, by building locally
>> on VirtualBox or VMware Player from installation media and exporting a
>> VM image to import on for an AWSM AMI. It does require some caution:
>> encrypting your root disk images, for example, is considered a good
>> security step. But XFS on CentOS 7 used to present some difficulties,
>> and I wound engaging in some serious "use my own tools to transfer the
>> running OS to a pristine new disk image partitioned the way my client
>> demanded to follow their security standards. I've been pulling that
>> stunt since roughly 1998 when updating and repartitioning operating
>> systeems for a Very Large CDN, the experience is helpful for dealing
>> with mock and chroot dcages.
>> _______________________________________________
>>
>
> Hi,
>
> Can Red Hat/IBM/Community do something to help?
>
> thanks

Sharing a popular AMI out of your own personal account can become....
expensive, for an individual, especially if it's a bit on the buiky
side with graphical applications or development tools. There also may
be bureaucratic or business goal reasons for AWS to delay CentOs 8: I
hope there is no subtle interference going on behind closed doors.
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel