I launched an instance on EC2 with a Debian 7.6 AMI and the system log is empty. Is that by design? With the ubuntu images, the server's ssh keys were accessible via the system log. What is the procedure for verifying the server fingerprint on debian? Must I generate and add my own key, with user data? I'd sure prefer not to do that.
2
-
I'm not sure if this is the case here, but frequently the console logs take 10-15 minutes to appear on the web console or be available via the EC2 API.– EEAAAug 12, 2014 at 23:57
-
@EEAA I waited almost an hour.– Aryeh Leib TaurogAug 20, 2014 at 12:57
Add a comment
|
2 Answers
Presumming you are talking about the ssh host key (and not keys for user accounts).
I suppose it depends on how the installation was performed. Most Linux systems will generate new ssh host keys when sshd is initially started. Interesting in that I thought these keys were in a specific file and not contained in any log file. Perhaps the ssh package was not automatically installed with that version of the instance?
BTW, ssh keys (public and private) for specific accounts would need to be manually generated and installed.
-
The other ec2 images I've worked with (ubuntu and coreos) log the ssh host key (or its fingerprint) in the system logs when it is generated so that the user can retrieve it securely from aws. The problem here isn't merely that part of the log missing, which might result if the ssh package were inexplicably absent. The whole log is empty or inaccessible. Aug 13, 2014 at 7:24
-
The ssh keys for the default user are configured before launch and injected by ec2. Aug 13, 2014 at 7:26
This is a bug in the debian HVM images.