[ECS] [Feature request ]:

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

When ECS Cluster is created it does not account for Customer's SCP Policy that mandates tags for resources being created and launches default template.
It will be advantageous to customers who have SCP mandating for tags to be able to include, and propagate them upon resource creation of the cluster.

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR
ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Currently if customer wants to create an ECS cluster compliant with SCP, the customer needs to create an empty cluster and then manually create resources and tag them or use and customise templates. This is a lot of customisation prone to errors as well.

Start by reviewing how ECS clusters are created and how the default template provisions their resources. Determine how customer-supplied tags could be included and propagated during resource creation, then verify that the resulting cluster resources comply with tag-mandating SCP policies.

Written by the indexing model from the issue text.