Hi Badra,
 To your question, the ssh key permission should be 600. In your case you
set it as 644.
Please change it to 600 using : chmod 0600  bhadra.pem
And try running the play.
Also please change the subject.

regards,
Ramu

On Thu, Aug 2, 2018 at 3:00 AM Durga Prasad <
[email protected]> wrote:

> Hi BADRAJ ANGIREKULA,
>
> Please give permission for your key use below of commands :-
>
> $ sudo chmod  0644  bhadra.pem
>
> Thanks & Regards,
> Durgaprasad
>
>
> On Thursday, August 2, 2018 at 1:24:51 PM UTC+5:30, Badraj Angirekula
> wrote:
>>
>> Hi all I am facing error in aws please help.
>>
>>
>> [root@server2 ~]# ssh -i bhadra.pem
>> [email protected].
>> amazonaws.com
>> The authenticity of host '
>> ec2-50-112-6-190.us-west-2.compute.amazonaws.com
>> (50.1
>> 12.6.190)' can't be established.
>> ECDSA key fingerprint is 1f:1b:6b:13:d2:7a:b5:a4:4b:78:84:b7:98:05:ab:39.
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added '
>> ec2-50-112-6-190.us-west-2.compute.amazonaws.com,50.
>> 112.6.190' (ECDSA) to the list of known hosts.
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> Permissions 0644 for 'bhadra.pem' are too open.
>> It is required that your private key files are NOT accessible by others.
>> This private key will be ignored.
>> bad permissions: ignore key: bhadra.pem
>> Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
>>
>> Thanks & Regards,
>> BADRAJ ANGIREKULA
>>
>> On Thu, Aug 2, 2018 at 2:45 AM, Kai Stian Olstad <
>> [email protected]> wrote:
>>
>>> On 01.08.2018 22:57, Kai Stian Olstad wrote:
>>>
>>>> It has support for a bunch of languages but the prompt need to be
>>>> "<some_word>'s password" or "password" for English and it's case
>>>> insensitive.
>>>>
>>>
>>> Correction, the strings must be "<some_word>'s password: " or "password:
>>> ".
>>>
>>> --
>>> Kai Stian Olstad
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ansible-project/7ee310d428f93ca90e2ae787c4c1c8b7%40olstad.com
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/0b283aae-bf92-4a74-b68c-307500a00b7e%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/0b283aae-bf92-4a74-b68c-307500a00b7e%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/CAAfqp0UjsZ5DVahgRNWABYtmNodD8NQyED0www7Gk5TOSBeUYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to