I was able to resolve my issue by explicitly added the ena and nvme drivers to the dracut configuration and re-running dracut:
echo 'add_drivers+=" ena "' >> /etc/dracut.conf.d/ena.conf
echo 'add_drivers+=" nvme "' >> /etc/dracut.conf.d/ena.conf
dracut -f -vvvv
This was not needed for Rocky OS v. 8.4, but is needed for v. 8.5.
It didn't even occurred to me that one should be able to do that, I generally consider instances to be disposable. Anyway, this doesn't answer your question.
This seems to suggest you can't use an EBS in us-east-1a for an instance in us-east-1c (eg, the volume needs to be in the same az as the instance). They also suggest that you can make a snapshot across regions (eg, snapshot your existing volume in the zone you want to "move" your instance). This could help with the "volume was not detected" problem. (you will be starting the new instance with the snapshot, not the original volume).
For future proofing, I would (resources permitting) rework the system and split the instance in 2 parts: one volume for the software that should be disposable (you should have an automated way to deploy the software and configuration) and one separate volume for the data (and this is the one you backup and snapshot and babysit :) )
Cannot start EC2 instance after changing its typeasked 3 years ago
T2 vs T3 Instance typeAccepted Answerasked 2 years ago
Change instance from t2.nano to t4g.nanoasked 17 days ago
Existing t2.micro instance updated to t3.micro with Ubuntu 20.04 upgrade - no network interfaceasked 9 months ago
The instance has not stopped after force to stop by action menu.asked 2 years ago
EC2 instance fails to start after changing instance type from t2 to t3asked 8 months ago
Convert a t2 instance to t3asked 4 years ago
Instance upgraded from t2 to t3 is not booting upasked 6 months ago
EC2 instance failure, wont startAccepted Answerasked 8 months ago
stop link is greyed out for t3.medium EC2 instanceasked 3 years ago