AWS EC2 : ERROR Invalid SSH key

[Faruque Azam]

Thanks Kapil.

Addition to you guidance I have added 22 ports to AWS Juju's security group
and I saw it was working perfectly.

I felt juju is not at all a better solution as it is creating number of
small instances for each service which will cause a high Amazon's bill. If
it would create all the services in a single instance that made sense.

Hope juju will update its nature.

Regards

Faruque

On Fri, Apr 5, 2013 at 9:52 PM, Kapil Thangavelu <
kapil.thangavelu at canonical.com> wrote:

>
> Your pointing authorized-keys-path to the host/client's authorized keys
> file.. which means you would need the private key there as well to be able
> to utilize juju. Juju populates the env with the public keys, but the
> client establishes a secure tunnel via executing ssh which means the
> private key needs to be accessible. Its not clear thats the case in your
> setup.
>
> As a quick workaround, remove authorized-keys-path from the
> environment.yaml..
> $ juju destroy-environment
> $ ssh-keygen -t dsa
>
> pick default paths for the new key
>
> juju bootstrap again, and things should work.
>
> hth,
>
> Kapil
>
>
> On Fri, Apr 5, 2013 at 11:03 AM, Faruque Azam <engrfazam at gmail.com> wrote:
>
>> Hi Peter,
>>
>> Thanks for your reply. I appreciate this very gladly. yes I have =>
>> authorized-keys-path: /root/.ssh/authorized_keys
>>
>>
>>  I have following configuration on my environment:
>>
>> environments:
>>
>> sample:
>>
>> type: ec2
>>
>> access-key: [my own key - did not show this here]
>>
>> secret-key: [my own key - did not show this here]
>>
>> control-bucket: juju-2ee78dee6e3340eb9fa5c2c10683a889
>>
>> admin-secret: e488be2c55e04be2857a35f15ab20b86
>>
>> default-series: precise
>>
>> juju-origin: ppa
>>
>> ssl-hostname-verification: true
>>
>> authorized-keys-path: /root/.ssh/authorized_keys
>>
>>
>> ----------------
>>
>> Look forward to hearing from you.
>>
>>
>> Kind Regards,
>>
>>
>> Faruque
>>
>>
>> On Fri, Apr 5, 2013 at 8:53 PM, Peter M. Petrakis <
>> peter.petrakis at canonical.com> wrote:
>>
>>>
>>>
>>> On 04/04/2013 05:12 PM, Faruque Azam wrote:
>>>
>>>> Hi,
>>>>
>>>> I have search but as I am very new so I need a very clear help line with
>>>> commands to resolve this issue.
>>>>
>>>> The present status is:
>>>> root at domU-12-31-39-14-75-3C:~# juju bootstrap
>>>> 2013-04-04 21:08:41,444 INFO Bootstrapping environment 'sample' (origin:
>>>> ppa type: ec2)...
>>>> 2013-04-04 21:08:41,633 INFO juju environment previously bootstrapped.
>>>> 2013-04-04 21:08:41,634 INFO 'bootstrap' command finished successfully
>>>> root at domU-12-31-39-14-75-3C:~# juju status
>>>> 2013-04-04 21:08:48,396 INFO Connecting to environment...
>>>> 2013-04-04 21:08:48,634 ERROR Invalid SSH key
>>>> 2013-04-04 21:09:18,696 ERROR Invalid SSH key
>>>> 2013-04-04 21:09:48,889 ERROR Invalid SSH key
>>>> 2013-04-04 21:10:18,986 ERROR Invalid SSH key
>>>>
>>>> I have been trying from last more than 6 hours - but failed :(
>>>>
>>>> Please help me.
>>>>
>>>
>>> You're using ssh as root? That's not necessary and may even cause
>>> problems.
>>>
>>> Double check the public keys included in environments.yaml
>>> authorized-keys.
>>>
>>> https://juju.ubuntu.com/docs/**provider-configuration-ec2.**html<https://juju.ubuntu.com/docs/provider-configuration-ec2.html>
>>>
>>>
>>>
>>>> Regards,
>>>>
>>>> Faruque
>>>>
>>>>
>>>>
>>>>
>>> --
>>> Juju mailing list
>>> Juju at lists.ubuntu.com
>>> Modify settings or unsubscribe at: https://lists.ubuntu.com/**
>>> mailman/listinfo/juju <https://lists.ubuntu.com/mailman/listinfo/juju>
>>>
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20130407/b715a0bf/attachment.html>