[ECS Fargate] [request]: Request to increase maximum ephemeral storage size for Fargate tasks (beyond 200 GB)

### 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**
Please consider increasing the maximum ephemeral storage limit for **Fargate** tasks beyond the current 200 GB.
A higher limit - for example, up to 1TB, would greatly help workloads that need substantial temporary space during runtime.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Some workloads process large temporary datasets, build intermediate files, or perform heavy I/O operations that require large but non-persistent storage.
For these cases, attaching EBS or EFS volumes is not ideal because:
We do not need persistence after the container stops.
We want storage that is automatically created and destroyed with the task.
Using EBS/EFS adds unnecessary management complexity and cost.

No repository file, test, or implementation entry point is named. Start by reviewing the Fargate 200 GB ephemeral-storage limit and the EBS/EFS alternatives described in the issue; done would require an AWS service decision or a documented increase to the task storage limit.

Written by the indexing model from the issue text.