Also, for whatever it's worth, I've tried putting the keys in ~/.boto, but the result is the same.
On Tuesday, November 24, 2015 at 2:03:51 PM UTC-5, Rob Wilkerson wrote: > > I thought this would be the easiest part of creating a dynamic inventory, > but I'm having a hell of a time connecting: > > boto.exception.NoAuthHandlerFound: No handler was ready to authenticate. 1 > handlers were checked. ['HmacAuthV4Handler'] Check your credentials > > In my <project>/ansible/development/ directory, I have ec2.py and ec2.ini > files: > > # <project>/ansible/development/ec2.ini > -- snip -- > boto_profile = Client > > # ~/.aws/credentials > [DifferentClient] > aws_access_key_id = <DIFFERENT_CLIENT_ACCESS_KEY> > aws_secret_access_key = <DIFFERENT_CLIENT_SECRET_KEY> > region = us-east-1 > output = json > > [Client] > aws_access_key_id = <PROJECT_ACCESS_KEY> > aws_secret_access_key = <PROJECT_ACCESS_KEY> > > The keys are for my IAM user with admin privileges and work just fine when > specified directly in the ec2 module. > > Any idea what I've got misconfigured here? I'm running Ansible 1.9.4. > > Thanks. > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f9cbdaef-0ee4-401e-b9af-39364a4a72be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
