S3 bucket access with env auth and region env variable relation

Hello experts,

Rclone version : 1.69

I have 2 rclone remotes created in rclone pod where rclone k8 pod attached with my org service account -
And also an env variable set on this pod which is AWS_REGION = us-east-2, where "us-east-2" is where my org s3 bucket present.

Now with these below remotes -
I am able to access my org s3 bucket as pod attached with service account and env_auth=true is used.
(region set on env variable also correct for my org bucket)
Now I have a requirement to access my customer s3 bucket and for that I have created another remote "customer-s3-bucket".
This has to work with Assume Role access.(seton both cloud side is taken care)

But when I try to ls customer bucket it gives error saying I am using invalid region - it says I am trying with "us-east-2" but bucket in "us-east-1".
Now if I change env variable to 'export AWS_REGION = us-east-1' then I am able to access customer s3 bucket.

From this I felt it is relying on AWS_REGION env variable when env_auth=true.

But now I was expecting my org bucket access to fail since my org bucket is in "us-east-2" and env variable is now set to us-east-1 (to access customer bucket).
But I was wrong I am now ABLE TO ACCESS BOTH THE BUCKETS!
How this is working?


printenv | grep AWS_REGION

AWS_REGION = us-east-2

[myorg-s3-bucket]
type = s3
env_auth = true
provider = AWS
region = us-east-2
secret_access_key =
access_key_id =
bucket_policy_only = true
no_check_bucket = true


[customer-s3-bucket]
type = s3
env_auth = true
provider = AWS
profile = default
region = us-east-1
secret_access_key =
shared_credentials_file = /data/config/rclone/aws_creds/customer_remote
access_key_id =

cat /data/config/rclone/aws_creds/customer_remote
[default]
role_arn = arn:aws:iam::009*******25:role/pis-dev-snowflake-s3-access-role
region = us-east-1
external_id = arn:aws:iam::13*****87:role/awsgt10integration3

—————————————————

Any suggestion would be appreciated.

Thanks in advance,

Mahendra

please rclone selfupdate and test again.