Re: [ansible-project] How to trace/debug Ansible EC2 ?

Since the ec2 modules use boto, which doesn't really execute commands, your best bet is to run your playbook with the environment variable ANSIBLE_KEEP_REMOTE_FILES=1 set, and with -vvv. This will allow you to examine the modules left on the target system (most likely localhost) and run them

Re: [ansible-project] How to trace/debug Ansible EC2 ?

On Wed, Mar 16, 2016 at 3:57 PM, James Cammarata wrote: > Since the ec2 modules use boto, which doesn't really execute commands, > your best bet is to run your playbook with the environment variable > ANSIBLE_KEEP_REMOTE_FILES=1 set, and with -vvv. This will allow you to

[ansible-project] How to trace/debug Ansible EC2 ?

Hello I have a problem with a simple Ansible playbook which launch an EC2 instance. The instance configuration is slightly different (different block-device-mapping) when I launch the same AMI from EC2 dashboard. To debug, I would like to see the exact AWS command Ansible/Boto runs.