On Fri, Feb 26, 2021 at 07:41:28AM -0500, David H. Rhodes Clymer wrote: > I have been building my own AMI for use at AWS because reasons. > However, in order to make my images acceptable, I end up having to > install the linux-image-3.16.0-.. image from Debian 8 (I think?). Any > other kernel I use produces a rejection from amazon's image-import. > > This document: > > https://docs.aws.amazon.com/vm-import/latest/userguide/vmie_prereqs.html#vmimport-operating-systems
The VM Import service targets a very specific use case involving migration of existing virtual machines from on-premesis environments to EC2. It isn't a general purpose AMI creation tool. > Clearly indicates that they do not support any version of debian > greater than 8.0, and they seem to mean it. As I mentioned, I've > worked around this by uploading with an old kernel as the default, and > then upgrading after. I didn't actually realize that VM Import claimed support for any Debian version, but apparently it supports "Debian 6.0.0-6.0.8, 7.0.0-7.8.0, 8.0.0". IMO it should either update that list to reasonably modern Debian versions and drop the old EOL versions, or just drop Debian support altogether if they can't update the list. > Clearly the official Debian EC2 AMI is running the latest debian > kernel. I'm curious how that AMI gets uploaded, and if I'm missing a > trick. We don't use VM Import. We use the ImportSnapshot API. See the following: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ImportSnapshot.html https://salsa.debian.org/cloud-team/debian-cloud-images/-/blob/master/src/debian_cloud_images/cli/upload_ec2.py https://docs.aws.amazon.com/cli/latest/reference/ec2/import-snapshot.html noah
