EKS S3 cross account authorization issue - oidc provider

Our S3 account exist in AWS account 344230057588 and OIDC enabled EKS in 456476723052. We have configured iam policy for S3 access and enabled trust policy for EKS oidc provider. We were able to annotate the EKS pod's service account with this iam role but the pod at run time which has Java code is not able to assume the custom role created by us but instead picking up the default node arn. We would like some direction on troubleshooting this issue and to force the java application to pick our custom role

sample logs, when we print identity.arn() where u can see node arn getting invoked.