[Fargate] [driver]: gelf is not a valid log driver

### 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**
What do you want us to build?
1.0.13

**Which service(s) is this request for?**
Fargate, 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.

I'm doing a setup to send the fargate container logs to graylog (ec2), is there any prediction to add this updated driver

The request concerns Fargate and ECS container logging to Graylog through the GELF driver. Start by checking the currently supported Fargate log drivers and the AWS containers roadmap; done would mean a documented or delivered path for using GELF with Fargate, but the issue does not identify files or tests.

Written by the indexing model from the issue text.