The speed-difference between #EC2Launch and #cloud-init is pretty stark. When I fire up a #Linux instance that has a #userData payload, doing:
sleep $(( 60 * 2 )) ; ssh <USER>@<INSTANCE_ID>Is usually sufficient to get me a login. If I launch a Windows-based EC2, I usually have to do:
sleep $(( 60 * 10 )) ; aws ssm start-session --target <INSTNCE_ID>Unless I want the dreaded "not available error". Worse, while two-minute pause for the cloud-init/Linux EC2 usually logs me in with the
cloud-init content well underway, the
#SSM login, after a ten-minute pause, usually has me arriving well before EC2Launch has even finished unpacking its data to start executing powershell scripts. It's like "dafuq is taking you so long??"