[service] [request]: EKS Fargate Console Exec - Web-Based Container Access in Management Console

### 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 Feature Request is regarding EKS Fargate Console Exec plugin to access the containers from the Web Based Interface.

The Current State is Users must use kubectl CLI to access Fargate containers, requiring local configuration and authentication setup.

What we need as the Users of EKS is:

#Proposed Solution.
Enable direct container shell access from the EKS console with:
• One-click terminal access from pod details page
• Built-in web terminal with session logging
• IAM-based access control integration
• Support for interactive shells and command execution

# Business Impact
• Eliminates kubectl setup complexity for troubleshooting
• Improves security through centralized access control
• Reduces operational overhead for development teams
• Provides feature parity with ECS container management

**Which service(s) is this request for?**
This could be EKS on Fargate Infrastructure

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The Current State is Users must use kubectl CLI to access Fargate containers, requiring local configuration and authentication setup.
We would want to Enable direct container shell access from the EKS console.

**Are you currently working around this issue?**
Using kubectl we authenticate with the EKS Cluster & access the container.

**Additional context**
Provides feature parity with ECS container management.

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No files, tests, or code entry points are identified; start by reviewing the requested EKS Fargate Console Exec behavior and the existing kubectl-based access described in the issue. Done would require a defined console workflow covering one-click pod access, a web terminal, session logging, IAM access control, and interactive command execution.

Written by the indexing model from the issue text.