[GH-ISSUE #1860] AWS CLI credentials other than $ HOME or less #946

New issue

Open

opened 2026-03-04 01:50:08 +03:00 by kerem · 5 comments

kerem commented

2026-03-04 01:50:08 +03:00

Owner

Originally created by @ggtakec on GitHub (Jan 14, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1860

There is a request to read the credential information(and region information) from the files(.aws/credential and config), which are the configure files of AWS CLI.
Those are different from the format of the passwd-s3fs file, but with the same credential information.

I would like to consider whether or not this should be supported.

Related - #1855

Originally created by @ggtakec on GitHub (Jan 14, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1860 There is a request to read the credential information(and region information) from the files(.aws/credential and config), which are the configure files of AWS CLI. Those are different from the format of the passwd-s3fs file, but with the same credential information. I would like to consider whether or not this should be supported. - Related - #1855

kerem commented

2026-03-04 01:50:09 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 14, 2022):

Duplicate of #1122.

@ggtakec commented on GitHub (Jan 14, 2022): Duplicate of #1122.

kerem commented

2026-03-04 01:50:09 +03:00

Author

Owner

@siketyan commented on GitHub (Jan 14, 2022):

@ggtakec
You s3fs-fuse already supports .aws/credentials file to read credentials from $HOME e.g. /home/$USER/.aws/credentials.
The option I suggested is to read this file from other location.

Background:
In MSYS2 environment, getting the home directory returns "/home/$USER" instead of "C:\Users$USER" for their compatibility. This behaviour blocks s3fs-fuse on Windows to read the file out of MSYS2 shell.

@siketyan commented on GitHub (Jan 14, 2022): @ggtakec You s3fs-fuse already supports .aws/credentials file to read credentials from `$HOME` e.g. `/home/$USER/.aws/credentials`. The option I suggested is to read this file from other location. Background: In MSYS2 environment, getting the home directory returns "/home/$USER" instead of "C:\Users\$USER" for their compatibility. This behaviour blocks s3fs-fuse on Windows to read the file out of MSYS2 shell.

kerem commented

2026-03-04 01:50:09 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 14, 2022):

Reopen this.

@ggtakec commented on GitHub (Jan 14, 2022): Reopen this.

kerem commented

2026-03-04 01:50:09 +03:00

Author

Owner

@gaul commented on GitHub (Jan 21, 2022):

We should follow the precedent of AWS CLI (and related SDKs) as closely as possible:

https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-where

As I understand it get_access_keys should consider %UserProfile% when using Windows. In addition to consistency, this will allow the project to transition to the AWS C++ SDK some day #1068.

@gaul commented on GitHub (Jan 21, 2022): We should follow the precedent of AWS CLI (and related SDKs) as closely as possible: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-where As I understand it `get_access_keys` should consider `%UserProfile%` when using Windows. In addition to consistency, this will allow the project to transition to the AWS C++ SDK some day #1068.

kerem commented

2026-03-04 01:50:09 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 22, 2022):

For Windows, let's use %UserProfile% instead of $HOME.(After #1855 pr)

@ggtakec commented on GitHub (Jan 22, 2022): For Windows, let's use `%UserProfile%` instead of `$HOME`.(After #1855 pr)