I also tried: ec2-register -n pvami -s snap-0ffe4a3cb9932b167 --virtualization-type paravirtual to see if I could force the ami to paravirtual, but this didn't work either. The ami is still listed as hvm.
Thanks for getting back to me, Rodney. I checked and when I create the AMI I cannot select a kernel. It just says it is going to use the default. I never selected one before, honestly. I've checked a few other snapshots, both from the same ec2 I am using and others from different ec2's (All using paravirtual).
Creating AMI from snapshot won't accept paravirtual virtualization typeAccepted Answerasked 22 days ago
RDS Snapshot stuck in Creating 0% state in Singapore Regionasked 4 years ago
Auto restore DB from snapshot or backupasked 2 months ago
CDK: How to restore a Redshift from a Snapshot ?asked 5 months ago
New lightsail instance from snapshot without sysprepasked 8 months ago
Restore encrypted Snapshotasked 4 months ago
Cannot restore RDS snapshotasked 6 months ago
Lightsail launch script not working when creating instance from manual snapshotasked a month ago
May I restore a backup snapshot on original instance in AWS lightsail?asked 3 years ago
Doubt about billing and transfers between regions of a Public AMI with public Snapshotasked 6 months ago