For role based access from EKS, we may approach this in two ways. The easiest way to do this is to attach the required policy directly to the underlying node (or nodegroup used in the cluster)
But this is not easily replicable in fargate pods. Also there is no way to contol access to specific policies for specific namespaces or pods in the cluster.
Another way to do this is through service accounts
(which is recommended best practice for kubernetes).
This does require the kubernetes OIDC provider to be registed to the eks account. If it is an eks cluster it can be easily done with