# EC2 module : dependency between exact\_count and count\_tag

**URL:** <https://forum.ansible.com/t/ec2-module-dependency-between-exact-count-and-count-tag/15889>\
**Category:** Ansible Project\
**Created:** [August 8, 2014, 1:51pm UTC](https://forum.ansible.com/t/ec2-module-dependency-between-exact-count-and-count-tag/15889 "2014-08-08T13:51:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![casimir\_Jeanjean](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@casimir\_Jeanjean](https://forum.ansible.com/u/casimir_Jeanjean)\
**Post date:** [August 8, 2014, 1:51pm UTC](https://forum.ansible.com/t/ec2-module-dependency-between-exact-count-and-count-tag/15889/1 "2014-08-08T13:51:18Z")

</div>

Hi everyone,  
In one of my plays, in a EC2 action, I used the “exact\_count” parameter and forgot to specify “count\_tag”. Ansible tried to kill one of my EC2 machines randomly (fortunately it had API termination disabled).  
In such case, as exact\_count and count\_tag are dependent of each other (according to the doc), shouldn’t the task have failed and told me “count\_tag” was missing ? Or are there any use cases for exact\_count alone ?  
Thank you in advance.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 8, 2014, 11:29pm UTC](https://forum.ansible.com/t/ec2-module-dependency-between-exact-count-and-count-tag/15889/2 "2014-08-08T23:29:06Z")

</div>

Ouch, absolutely should have.

There’s a flag “required\_together” in the argument spec that can be used for this.

Can you please file a ticket in GitHub so we can take care of this one?

Random killing of nodes is definitely not something we wish to encourage! Sometimes nodes deserve it though, but not this time.

–Michael