[ECS] [AWS for Fluent Bit]: Support ECS Task metadata injection when running Fluent Bit as a Daemon Service
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### 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**
Support ECS Task metadata injection when running Fluent Bit as a Daemon Service. FireLens can inject metadata but it requires running Fluent Bit as a sidecar. There is no nice way to inject task metadata in logs when running Fluent Bit as a daemon.
**Which service(s) is this request for?**
ECS
Contributor guide
Research direction
The issue mentions ECS, Fluent Bit, FireLens, and daemon services but names no repository files, tests, or entry points. Start by researching ECS task metadata injection and the differences between daemon and sidecar deployments. Define the supported metadata, configuration path, and validation criteria before implementation; done means task metadata appears reliably in daemon-service logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100