[Fargate] [request]: Setting EFS/NFS Client Cache Options for Containers when using FARGATE as Compute Resource.

### 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?

SETTING EFS/NFS CLIENT CACHE OPTIONS FOR CONTAINERS WHEN USING FARGATE AS COMPUTE RESOURCE.

**Which service(s) is this request for?**
This could be Fargate, ECS, EKS, ECR

For AWS Compute Service: Fargate
working with
AWS Storage Service: EFS

And should be usable with AWS Container Environment/Services: ECS, EKS
with AWS APIs (for example only, NOT exhaustively listed): AWS CLI, AWS CoPilot, AWS CloudFormation, etc.

==============================================================

Hi:
This is a FEATURE REQUEST for
SETTING EFS/NFS CLIENT CACHE OPTIONS FOR CONTAINERS WHEN USING FARGATE AS COMPUTE RESOURCE.

The need is to DISABLE EFS/NFS Client Cache so the Applications running in multiple Containers in Fargate Compute Environment
will have their mounted shared file systems be up-to-date between containers.
This is for Linux Applications that require synchronized File System for Processing in multiple Containers.

Please note this Request was originally an AWS Support Center Case (ID 9734954461 created 2022-03-07T02:46:47.533Z).
With the Support Center Personnel indicating:
"With ECS Fargate, it is NOT POSSIBLE to use the NFS mount options(NFS/EFS Client Cache Option Selections)."
"With AWS Fargate NOT CAPABLE (as of March 23, 2022) of handling NFS/EFS CLIENT Cache Option Specification/Selection."

With Fargate as the Compute Resource for Containers,
How to perform "SETTING EFS/NFS CLIENT CACHE OPTIONS" ?

Trying to achieve Maximum Cache Coherency at multiple (double/triple digits) NFS/EFS Clients (Containers) over
an AWS ECS Fargate Environment.

Need to Set NFS/EFS Client Options of:
noac DisAble Cache File Attributes at NFS/EFS Client.
lookupcache=none DisAble Directory LookUp Cache.
cto Use "close-to-open" cache coherence semantics for directories.
local_lock=none For all the locks to be NOT local.
sharecache Don't think this matters in Single Application-Service in Multiple Containers over Fargate Environment.

Solution(s) using any AWS API(s) is(are) welcomed.

Please let me know if additional information is needed.

Thank You very much!

==============================================================

**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.

**Are you currently working around this issue?**
How are you currently solving this problem?

**Additional context**
Anything else we should know?

**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.)

The issue names no repository files, tests, or entry points. Start by reviewing the Fargate, EFS/NFS, ECS, and EKS service documentation and API capabilities; done would mean a documented or implemented way to select the requested client cache options for Fargate containers.

Written by the indexing model from the issue text.