[EKS][Fargate] [request]: Transparent EKS fargate management

### 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**
Transparent management for EKS Fargate

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

EKS Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

### Detail documentation

It would be great if AWS can provide a detail documentation as the way Kubernetes describes its items

### No Fargate log

Lately, I suffered an uncomfortable experience when debugging the fargate issues after updating my cluster to version 1.15. The only thing is documented about fargate pod cannot scheduled is:

> Pods which do not match a Fargate profile may be stuck as Pending. If a matching Fargate profile exists, you can delete pending pods that you have created to reschedule them onto Fargate

In my case, there is no issue with the Fargate profile. But no useful log or error log could be found on Cloudwatch for troubleshooting .

### No resource visualize

There is no fargate history or metrics could be found on either the console or cloudwatch. I think the metrics like Lambda would be really helpful. And comming with cloudwatch integration, the alarms are needed also

The request concerns EKS Fargate, CloudWatch, and Kubernetes-style resource descriptions; no repository files or tests are identified. Start by separating transparent management, troubleshooting logs, resource history and metrics, and alarms into concrete scope. Done would require an agreed AWS capability and corresponding roadmap or documentation outcome.

Written by the indexing model from the issue text.