Re: How to get server ssh keys on debian ec2 instance?
It works with the pv image.
I'm still not getting the system log with the hvm ami, ami-0632fd6e.
I've tried the hvm ami in other regions as well, with no success.
I had the same experience with an earlier release several months ago.
I have tried with various instance types. Instance checks were ok.
I waited over half an hour. I used standard root ebs device only.
When I try "Get System Log" on the AWS console, it just shows a blank
I blindly accepted the fingerprint reported by ssh and was in fact
able to log in to the machine. I don't want to do that, though.
Could it be the console isn't going to the right place on the hvm image?
On Tue, Aug 12, 2014 at 06:53:51PM -0400, leprechaun wrote:
> I'm running ami-c4ab67ac in us-east-1, and can confirm that I get a
> system log, which outputs all of the server's SSH key fingerprints.
> What does the instance status checks say? 2/2?
> Can you ping the machine? does it respond in any way?
> Has it been over 4-5 minutes since you launched it?
> Did you do anything funky with block device attachments?
> On Tue, Aug 12, 2014 at 6:20 PM, Aryeh Leib Taurog <email@example.com> wrote:
> > I just launched an instance on EC2 with a Debian 7.6 AMI from here:
> > <https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy>
> > 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?
> > Regards,
> > Aryeh Leib Taurog
> > --
> > To UNSUBSCRIBE, email to firstname.lastname@example.org
> > with a subject of "unsubscribe". Trouble? Contact email@example.com
> > Archive: 20140812222031.GE6833@deb76.aryehleib.com">https://lists.debian.org/20140812222031.GE6833@deb76.aryehleib.com
> Rusty Russel said that any one quoting him in an email signature was
> an idiot. Does paraphrasing count?