When rebooting a RancherOS AMI through AWS EC2, reboot times seem crazy long.
60+ seconds vs the 5 seconds I’m seeing locally.
I first noticed this after rebooting post-upgrade to 3.3 and thought it might be because the update process was doing something extra. But even a standard
sudo reboot does the same thing.
Is this an overhead that EC2 adds, or something in the AMI itself?