An application will run on an Amazon EKS cluster backed by Amazon EC2 nodes and must use an Amazon EFS filesystem through the installed EFS CSI driver. The EKS EC2 nodes fail to mount the EFS filesystem. Which remedies will resolve the issue? (Choose three.)

EFS mount failures from EKS nodes typically stem from networking, permissions, or mount target availability. Adding a security group inbound rule on the EFS filesystem to allow NFS (port 2049) traffic from the EKS cluster nodes is crucial. EFS uses NFS, and without this rule, the EKS nodes cannot establish a network connection to the EFS filesystem. Creating an IAM role that grants the Amazon EFS CSI driver the necessary permissions is essential. The CSI driver requires specific IAM permissions to create and manage EFS access points and interact with the EFS API on behalf of the pods. Creating an EFS mount target in the same subnet used by the EKS EC2 nodes ensures network reachability. EFS requires a mount target in each subnet where clients (EKS nodes) need to access the filesystem. Migrating to Fargate is not a direct solution to EFS mount issues on EC2 nodes. AWS DataSync is for data transfer, not resolving mount failures. Disabling EFS encryption is not a common troubleshooting step for mount failures and compromises security.