# Add support for tagging ECS Cluster to community.aws.ecs\_cluster

**URL:** <https://forum.ansible.com/t/add-support-for-tagging-ecs-cluster-to-community-aws-ecs-cluster/45560>\
**Category:** Collection Development\
**Tags:** aws\
**Created:** [March 18, 2026, 8:37pm UTC](https://forum.ansible.com/t/add-support-for-tagging-ecs-cluster-to-community-aws-ecs-cluster/45560 "2026-03-18T20:37:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaps](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shaps/32/1356_2.png) [@Shaps](https://forum.ansible.com/u/Shaps)\
**Post date:** [March 18, 2026, 8:37pm UTC](https://forum.ansible.com/t/add-support-for-tagging-ecs-cluster-to-community-aws-ecs-cluster/45560/1 "2026-03-18T20:37:46Z")

</div>

Hi all,  
I have been trying to get this PR merged for quite some time now [#2347](https://github.com/ansible-collections/community.aws/pull/2347) and I seem to be getting nowhere. While I do understand people are busy, it would still be nice if somebody showed some love to the PR, at least some interactions in the comments would be nice. This is not a great experience from a contributor’s prespective.  
Think of a new contributor trying to get a PR merged for the first time, only to find out that it’s left open and uncommented for over a year.

Rant over 😃 I’d appreciate if I could get some traction on the PR ( I use this module daily at work and it would be nice if I didn’t have to maintain a private fork just to have tags )

Thanks!  
Shaps