Thanks for reporting, it certainly does seem to not be loading 😕

I would expect it to be loaded by the Default Region Provider, but it doesn't seem to be loaded. At least it seems to be loaded when specified by the environment variable AWS_REGION.

Also, although this is a separate this, it might be better to be able to set DEFAULT_REGION.

Thank you for looking into it
ap-northeast-1/s3/aws4_request</Message><Resource>/</Resource><Region>garage
Shows some part of the code knows the region and another part does not, this is quite an interesting bug

The new version of stu (0.6.0) now does a better error message: No bucket found (region: us-east-1) with stu --profile mail-server-wdes-intranet
Probably

Only needs to fix region loading now ?

The implementation up to 0.5.2 was as follows:

1. If --region is set, use it.
2. If AWS default value (environment variable, profile, etc.) is set, use it.
3. If none of them can be obtained, use the default value (ap-northeast-1).

In 0.6.0, users can now set the default value of 3 individually as a configuration.

On the other hand, this issue is about the profile value not being loaded correctly in 2.

Setting a default value may save you the trouble of specifying --region.

I am also seeing the issue, I would have expected the region from my aws profile to be used, but I have to specify it manually. Following.

https://github.com/lusingander/stu/releases/tag/v0.6.2

Thank you !
It works fine 🎉

Thanks for checking!