<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2"> </HEAD> <BODY LINK="#0000ff"> Hi Chris, Are you logging in as "ubuntu" as the user? Also, can you send the debug output (<A HREF="http://the.earth.li/~sgtatham/putty/0.58/htmldoc/Chapter4.html">http://the.earth.li/~sgtatham/putty/0.58/htmldoc/Chapter4.html</A> ). Thanks, Ben On Mon, 2011-08-29 at 12:14 -0400, Johnson, Chris M (Dublin) wrote: <BLOCKQUOTE TYPE=CITE> I’m experiencing a strange result in using an Ubuntu AMI on EC2 that doesn’t occur when using an Amazon Linux AMI. Your thoughts would be appreciated! When I create a new instance of ebs/ubuntu-images/ubuntu-natty-11.04-amd64-server-20110426 (ami-1aad5273), I pick an existing keypair. When the new instance starts up and I attempt to connect (using Putty), I get an error saying “Server refused our key”. When I read the server log, I can see new RSA and DSA keys are being generated. It appears the instance isn’t using my existing key pair. However if I spin up a new instance of the Amazon Linux AMI and follow the exact same procedure, I am able to connect using the existing key pair. Is there a difference between how SSH credentials are managed for Ubuntu and Amazon AMI’s? Or maybe I’m doing something wrong. Regards -- Chris </BLOCKQUOTE> <TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%"> <TR> <TD> -- Ben Howard <A HREF="mailto:ben.howard@canonical.com">ben.howard@canonical.com</A> Canonical USA GPG ID 0x5406A866 </TD> </TR> </TABLE> </BODY> </HTML>