aws / containers-roadmap

This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
https://aws.amazon.com/about-aws/whats-new/containers/
Other
5.21k stars 318 forks source link

[ECS] [Events]: Add resource tags to ECS events #2329

Open nhlushak opened 5 months ago

nhlushak commented 5 months ago

Community Note

Tell us about your request It would be very nice if ECS event's structure had aws resource tags included to it. It has a lot of information about container definitions of task (if we are speaking about Task State Change events) but not tags, which makes processing of these events feature limited for us.

Which service(s) is this request for? ECS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Our tech team has a lot of sub-teams working for different branches of business and we tag our resources accordingly to make sure all AWS resources are tagged according to system it is backing and team that maintains this system. Processing ECS events might also be done using these tags so they could be delivered to different notification channels based ob resource tags.

Are you currently working around this issue? Currently, we are doing the same thing, but with making event "enrichment" with invoking ECS API with Lambda, that receives original event.

monelgordillo commented 3 weeks ago

I use awsvpc, each ECS container, service, & task defintion includes tags for ApplicationName. However, the networkinterface does not include the related tags.

nhlushak commented 2 weeks ago

@monelgordillo I am not claiming that exact resources that ECS creates does not have resource tags. My point is that ECS Events that you can receive from EventBridge does not have any of them, which makes it harder to process these events with only general information. Which looks strange to me, since event structure is very similar to task definition's structure.