Assuming role configured in AWS profile does not work outside of `aws` partition (China, US Gov Cloud, etc.) about mountpoint-s3 HOT 5 CLOSED

To add to this, when I enable IMDS authentication I seem to be able to find the correct endpoint , but when I disable IMDS versions v1 and v2 the failure occurs!

from mountpoint-s3.

Thanks for the bug report, @csy97. Yes, it looks like a bug. Specifically, it looks like assuming a role is not working outside of the global regions - i.e. China, US Gov Cloud.

We'll continue looking into this - I'll provide an update soon.

from mountpoint-s3.

hello ,I noticed that this aws-c-auth seems to have fixed the problem and the project has updated the branch information for crt dependency, I would like to enquire when the new binary/rpm version of mount-s3 will be released!

from mountpoint-s3.

Hi @csy97, we have integrated the fix and we are adding integration tests for it. We plan to include it in the next release, but we cannot share a date for it, yet.

from mountpoint-s3.

Hey @csy97.

For this issue, we recommend that you put the configuration for the AWS profile in your AWS config file (typically ~/.aws/config) while the actual credentials live in your AWS credentials file (typically ~/.aws/credentials). (Or better yet, use short-term credentials if possible for this use case.)

For instance, we'd recommend this:

# in ~/.aws/config`
# "profile" below is important
[profile bwmtest2]
output=json
region=cn-northwest-1
role_arn=arn:aws-cn:iam::714736990101:role/s3fullrole
source_profile=default

# in ~/.aws/credentials`
[default]
aws_access_key_id = ak
aws_secret_access_key = sk

The benefit here is that you could share the config file and avoid sharing the credentials file.

I've just tested this use case in cn-north-1 with mountpoint-s3 v1.7.0 released today, storing the profile in a config file and credentials in a credentials file and it worked OK. Storing the profile configuration in the credentials file does not work, and we would not recommend it.

I'll close this issue for now, please re-open if you are still having issues.

from mountpoint-s3.