Check the version of boto. I ran into the same issue and found that the version of boto on the system was old enough that it wouldn't automatically pull in EC2 role credentials.
-Jharrod On Monday, January 13, 2014 9:40:00 AM UTC-7, Mark Casey wrote: > > I have a role that uses the ec2 module and it is working fine, so I'm > assuming I'm ok on dependencies like boto... but when I try to run *ec2.py > --list* I get back: > > root@ip-1-1-1-1:/etc/ansible/elastirax# ./ec2.py --list >> Looks like AWS is down again: >> EC2ResponseError: 401 Unauthorized >> <?xml version="1.0" encoding="UTF-8"?> >> <Response><Errors><Error><Code>AuthFailure</Code><Message>AWS was not >> able to validate the provided access >> credentials</Message></Error></Errors><RequestID> removed >> </RequestID></Response> >> > > That host is an ec2 instance itself. I tried it on another host (a > rackspace box) after exporting the credentials the exact same way and the > problem isn't there; both the role and ec2.py work there. > > I've tried comparing installed packages between the two hosts (both Ubuntu > 12.04.3, ansible 1.4.3) and using pip to make sure I have latest boto, but > I'm not sure how to troubleshoot from here. Do I need to do something to > run ec2.py on an ec2 instance...change a url to an internal one or > something? > > Thanks for any insight/suggestions, > Mark > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
