Is there a way to use this in eks without using a service account?

[michaelmohamed]

Is there a way to use this in EKS without using a service account?

I'd like to use the standard access token and secret with EKS.

When I install via

helm upgrade --install aws-mountpoint-s3-csi-driver \
    --namespace kube-system \
    aws-mountpoint-s3-csi-driver/aws-mountpoint-s3-csi-driver 

Pod creation fails.

17m         Normal    SuccessfulCreate   daemonset/s3-csi-node   Created pod: s3-csi-node-txcv6
17m         Normal    SuccessfulCreate   daemonset/s3-csi-node   Created pod: s3-csi-node-2lcm7
17m         Normal    SuccessfulCreate   daemonset/s3-csi-node   Created pod: s3-csi-node-kfvb7
7m39s       Warning   FailedCreate       daemonset/s3-csi-node   Error creating: pods "s3-csi-node-" is forbidden: error looking up service account kube-system/s3-csi-driver-sa: serviceaccount "s3-csi-driver-sa" not found
4m44s       Warning   FailedCreate       daemonset/s3-csi-node   Error creating: pods "s3-csi-node-" is forbidden: error looking up service account kube-system/s3-csi-driver-sa: serviceaccount "s3-csi-driver-sa" not found

[unexge]

Hey @michaelmohamed, our Helm chart should create and use service account s3-csi-driver-sa by default unless you pass node.serviceAccount.create=false.

If you really don't want to create/use a specific service account you might try setting node.serviceAccount.create=false and node.serviceAccount.name=default to not create a new service account and use the default service account for the namespace. But, that's something we don't test against and some things might not work.