# ecs\_tag **URL:** \ **Category:** Ansible Developer\ **Created:** [November 4, 2019, 5:47am UTC](https://forum.ansible.com/t/ecs-tag/31590 "2019-11-04T05:47:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_Pechner](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Michael\_Pechner](https://forum.ansible.com/u/Michael_Pechner)\ **Post date:** [November 4, 2019, 5:47am UTC](https://forum.ansible.com/t/ecs-tag/31590/1 "2019-11-04T05:47:29Z")
I wrote an ecs\_tag module based on the ec2\_tag code. It only handles tagging ecs\_clusters at the moment, since that is all I need. The boto3 ecs client call tag\_resources can tag services and tasks as well. Questions: First if I put in the effort to follow the process for creating test cases for a pull request, is there interest? Two, should I write it requiring ARN’s only like the boto3 call? Or allow ARN, cluster, service, task, task\_definition, or container parameters to allow the resource to be identified? ---
**Author:** ![Michael\_Pechner](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Michael\_Pechner](https://forum.ansible.com/u/Michael_Pechner)\ **Post date:** [November 12, 2019, 1:45am UTC](https://forum.ansible.com/t/ecs-tag/31590/2 "2019-11-12T01:45:09Z")
Are the crickets this groups manor of telling me there is no interest in this functionality? ---
**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\ **Post date:** [November 12, 2019, 2:06pm UTC](https://forum.ansible.com/t/ecs-tag/31590/3 "2019-11-12T14:06:32Z")
You might want to try the aws working group [https://github.com/ansible/community/tree/master/group-aws](https://github.com/ansible/community/tree/master/group-aws), probably a more focused audience to express interest on this. The irc channel is most likely to get you a more immediate response.