When I run rclone in EKS with IAM Roles for Service accounts it seems that the EC2 role is prioritized and picked before the EKS one. This is problematic in a default EKS setup because all the nodes will have an IAM role and there is seemingly no way to make it use the EKS role instead then.
I would have expected (I think most other tools that I have used does it this way) it to prioritize the EKS role and then use EC2 role as a fallback. Since it is optional to add an EKS IAM role you can always just not do that if you explicitly want to use the EC2 one.
Not sure if this counts as a bug or feature request though.
Bottlerocket Linux 64bit
rclone move --buffer-size=0 --error-on-no-transfer --no-check-dest --no-traverse --no-update-modtime --s3-env-auth --s3-no-check-bucket --s3-region=eu-central-1 --use-mmap "$SRC" "s3:$DEST"
No config file, only this env var: