4 ms·
I would appreciate serial console output that doesn't take 10x the boot time of an instance to propagate. Seriously, 30s boot time, 300s (or more!) to see that
by zdw 5y ago
I would appreciate serial console output that doesn't take 10x the boot time of an instance to propagate.
Seriously, 30s boot time, 300s (or more!) to see that serial console output via the GUI or API.
This is a PITA if you're using AWS for short-lived CI runners, and the console to check what the SSH host key is of these newly spun up nodes.
- deleted 5y ago[deleted]
- cperciva 5y agoWe have that now: There's an API option to say "give me the latest output instead of what you have cached". Why that isn't the default, I have no idea.
- paranoidrobot 5y agoI want something like a --follow option which acts like tail's follow option. aws ec2 get-console-output --instance-id xx --follow When debugging why an EC2 instance is having weirdness on boot, it's a pain to sit there refreshing logs constantly to see if it's got to that point yet.
- mdaniel 5y agoStrangely, at least from an outside observer's point of view, one would think the user's interests and AWS's interests would overlap for that one -- it doesn't square with my mental model that answering repeated polling requests to an endpoint which surely knows the last emitted text are cheaper than leaving the connection open and using any number of fancy http push mechanisms to send down updated content Or, if we really wanted to get crazy: use the new SSM protocol and push down the console log that way, since they have obviously already invested a ton of engineering into the protocol and its scaling concerns, extra bonus++ that it then would work from the EC2 Console, too
- MaxBarraclough 5y agoSeconded (although I admit I haven't tried cperciva's suggestion). This would make it quicker to view the SSH fingerprint of a new instance. AWS has added a web-based SSH client, which is quicker than waiting for the serial console output, but you need to dig out the relevant command to show the fingerprint. Aside: I may be one of very few people who bother to verify fingerprints. Why it seems to be the norm to hold SSH security to a much lower standard than HTTPS, by blindly trusting on first use, I don't know. I recently tried out Microsoft Azure, which appears to offer no way to view the RDP thumbprint of a new Windows Server instance. It's not that it's buried somewhere in the web UI, it simply isn't there. (If I'm mistaken on that point, a correction would of course be welcome.)