I initially just had id_rsa, then I had both files, but the id_rsa.pub was in puttygen format which is slightly different. The compute-example readme should be modified to say that the id_rsa.pub is necessary, or an error message the key couldn't be created. Thanks!
On Tue, Jul 23, 2013 at 5:12 PM, Andrew Phillips <[email protected]> wrote: > And in the Amazon GUI it shows up with a matching name and fingerprint >> under key pairs. So I guess when I try to login, using my id_rsa key (as >> the provided source does) it doesn't work because it created a new pair. >> > > AdminAccess.standard() should, by default, attempt to associate your > *public* key with whatever nodes it creates. Specifically [1], it will look > for > > System.getProperty("user.home"**) + "/.ssh/id_rsa.pub" > System.getProperty("user.home"**) + "/.ssh/id_rsa" > > both of which need to be UTF-8 files. If it can load those, it should > create a key pair in EC2 that matches the fingerprint of your local key. If > it is unable to load those, it will indeed generate a new key pair. > > Do you have both of those files, or perhaps only id_rsa? > > ap > > [1] https://github.com/jclouds/**jclouds/blob/master/compute/** > src/main/java/org/jclouds/**compute/config/**AdminAccessConfiguration.java<https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/config/AdminAccessConfiguration.java> >
