# A catch-22 in the ec2 provisioning examples (plugins/inventory/ec2.py doesn't allow for local host)

**URL:** <https://forum.ansible.com/t/a-catch-22-in-the-ec2-provisioning-examples-plugins-inventory-ec2-py-doesnt-allow-for-local-host/12822>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [May 17, 2013, 7:01pm UTC](https://forum.ansible.com/t/a-catch-22-in-the-ec2-provisioning-examples-plugins-inventory-ec2-py-doesnt-allow-for-local-host/12822 "2013-05-17T19:01:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [May 17, 2013, 7:01pm UTC](https://forum.ansible.com/t/a-catch-22-in-the-ec2-provisioning-examples-plugins-inventory-ec2-py-doesnt-allow-for-local-host/12822/1 "2013-05-17T19:01:31Z")

</div>

We already addressed this on in an IRC conversation.

You need to run provisioning playbooks when you want new nodes, and the provisioning playbook uses the ‘add-host’ module to add it to dynamic inventory, then there is a play at the bottom that runs the configuration roles/tasks on the host

Then you have another playbook that runs against the whole group for reconfig purposes.