We just moved to Packer.io for cloud image builds. That said, for our customized base image, I did a minimal CentOS 7 install on Hyper-V locally, added the kernel modules for NVMe and ENA support and followed the AWS guides: https://aws.amazon.com/ec2/vm-import/ and https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html and https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#in...

Also, when generating your AMI, make sure to set the Storage Optimized flag in case you want to take advantage of it. If you don't set it during image creation, the AMI won't be able to take advantage of it.

Gregory

-----Original Message----- From: CentOS-devel centos-devel-bounces@centos.org On Behalf Of john+centos@johnkeates.com Sent: June 2, 2019 11:52 AM To: centos-devel@centos.org Subject: [CentOS-devel] Building CentOS Cloud Images

I’m working on an internal build chain for AWS CentOS images, and I’m looking for any information regarding the changes or modifications made when creating the AMIs, aside from what’s already in the anaconda-ks file in currently uploaded AMIs. I know there isn’t much publicly available on the deployment source for CentOS-AWS images or how they are constructed in the first place, but any information on what’s added/removed on a base install would be great.

(p.s. I might have accidentally sent this message twice, but once from an unregistered email address, I hope the first one simply doesn’t reach the list)

Regards, John

_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel