[Fargate] [request]: Can we use Fluentd Log driver in fargate without using firelens

### 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**
This is related to the fluentd support in fargate. The earlier issue https://github.com/aws/containers-roadmap/issues/383, got closed pointing to firelens.

In our case, the ECS containers forward the logs to a fluentd aggregator which sends the logs into a kinesis stream.

From what I understand firelens does not support kinesis streams yet. So, is there a way to use fluentd directly from fargate containers without using firelens?

Basically, similar to how it works currently for ECS containers.

**Which service(s) is this request for?**
Fargate

**Additional context**
https://github.com/aws/containers-roadmap/issues/383

Start by reading the referenced containers-roadmap issue #383 and the request's description of ECS containers forwarding logs to a Fluentd aggregator and then Kinesis. Determine whether Fargate can support direct Fluentd logging without FireLens, and document a clear supported approach or the remaining limitation.

Written by the indexing model from the issue text.