# ec2\_eni module should honour description for uniqueness

**URL:** <https://forum.ansible.com/t/ec2-eni-module-should-honour-description-for-uniqueness/23399>\
**Category:** Ansible Developer\
**Created:** [January 6, 2017, 4:58pm UTC](https://forum.ansible.com/t/ec2-eni-module-should-honour-description-for-uniqueness/23399 "2017-01-06T16:58:07Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vasco\_Figueira](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@Vasco\_Figueira](https://forum.ansible.com/u/Vasco_Figueira)\
**Post date:** [January 6, 2017, 4:58pm UTC](https://forum.ansible.com/t/ec2-eni-module-should-honour-description-for-uniqueness/23399/1 "2017-01-06T16:58:07Z")

</div>

Hi,

Just filed [https://github.com/ansible/ansible/issues/19972](https://github.com/ansible/ansible/issues/19972)

“The ec2\_eni module does not create a new ENI and instead updates the description of an existing ENI that matches its other args. This is important for the cases when we don’t know the IP address nor want to attach it to an instance and just want to create an ENI.”

…and was looking at a possible fix.

I found the relevant commit: [https://github.com/ansible/ansible/commit/f8314c3e618c4050f8e957c780f66523111076c8](https://github.com/ansible/ansible/commit/f8314c3e618c4050f8e957c780f66523111076c8)

It does make me wonder if the change in behaviour (excluding the description and security groups from what identifies an ENI) wasn’t intentional. See find\_eni().

I’m happy to contribute a fix but would like input from Filipe and others on what makes more sense:

1. include back description and security\_groups attributes in the find\_eni filters;
2. instead allow for a state=created that expects the ID and IP address to be omitted and creates or fails but doesn’t update;
3. do nothing?

Thanks,

Vasco