Try chmod 400 instead of 600 and check if it gives same error On Thu, Aug 2, 2018, 14:33 Raymond Saga <[email protected]> wrote:
> You should limit the access to 600, try to run chmod 600 and try again > > On Thursday, August 2, 2018 at 3:54:20 PM UTC+8, 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 12:30 PM, D <[email protected]> wrote: >> >>> did you find this ? or how you are managing it, i am interested too. >>> >>> On Friday, 28 February 2014 02:00:51 UTC+5:30, [email protected] >>> wrote: >>>> >>>> I'm evaluating Ansible Tower as a way to manage configuration and >>>> deployment of applications. >>>> >>>> I've built a small application with an interface to the REST API to >>>> manage some of the more complicated steps in the deployment process (for >>>> example, logging a 'build' in the system upon a successful Jenkins job, and >>>> tracking its deployment to various environments), and there is one piece of >>>> the puzzle I can't figure out. >>>> >>>> We're using playbooks and templates to manage config files on servers >>>> in what seems to be a pretty standard way, with a 'project' set up for a >>>> branch of our playbooks git repository, but it doesn't look like there is a >>>> way of picking a particular git revision when executing a job. It would be >>>> really nice to, when triggering a job template, tell it which git commit >>>> (or tag) we want it to use, since config changes associated with a >>>> particular build can best be tracked by git commit, and not simply >>>> whatever's been pushed to a particular branch. One reason for this is, lets >>>> say we have changes to group_vars/prod that need to go out on the next >>>> push. If those changes were simply pushed to the prod branch of our >>>> repository in anticipation of the push, any new production servers brought >>>> up before the actual deployment process happened (that is, servers that >>>> would have the playbook executed on them between the commit and the actual >>>> deployment) would be erroneously getting the new settings. And I'm hoping >>>> to avoid complicating the otherwise push-button deployment process with a >>>> merge-to-a-git-branch step. >>>> >>>> Has anyone here dealt with this sort of use case? Is there a way around >>>> it? >>>> >>>> >>>> >>>> *tl;dr: Can I choose a specific scm tag or revision a job will run its >>>> playbooks from in Ansible Tower?* >>>> >>> -- >>> 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/6fa211dc-e5f0-4f6a-b0f1-4f15784c9841%40googlegroups.com >>> <https://groups.google.com/d/msgid/ansible-project/6fa211dc-e5f0-4f6a-b0f1-4f15784c9841%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/b2865153-8013-466e-bba6-0d0a6b5437b7%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/b2865153-8013-466e-bba6-0d0a6b5437b7%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/CAHKdPz6bZ7iSwirYQj2fexseyxa5j5OUsFq6k-n7rfoLU1qSvA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
