*typo: not --> now. there's a nice one-letter semantic change, lol.
On Thursday, November 12, 2015 at 4:38:16 PM UTC-5, nathan chu wrote: > > Hi, > > I recently inherited an Ansible deployment that manages some EC2 instances > and I have a couple questions. I am unable to find a pem file/ssh key on > the local file system, but somehow Ansible is able to connect to the > instances it creates and run shell scripts. How is this possible? I'm* > now *trying to enhance the existing playbooks to update some data via a > script on a central/master server in our deployment every time we create a > new instance, but I'm having trouble connecting to the instance. How can I > use whatever mechanism is in place for the recently provisioned instances > to access this single (relatively static) instance? > > Thanks, > > > Nate > -- 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/59ba986f-eee1-4cf8-8872-0cbccb8b6e18%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
