[GH-ISSUE #822] s3fs should use a .aws/credentials profile #475

New issue

Closed

opened 2026-03-04 01:45:57 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:45:57 +03:00

Owner

Originally created by @jeremyjjbrown on GitHub (Sep 19, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/822

I racking my brain as to why s3fs would ask for a custom formatted custom file for aws credentials when there is one right on every facile aws users system at ~/.aws/credentials.

I for one rotate my keys regulary using a tool. I think it would be wise to just support the default way of doing things.

Originally created by @jeremyjjbrown on GitHub (Sep 19, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/822 I racking my brain as to why s3fs would ask for a custom formatted custom file for aws credentials when there is one right on every facile aws users system at ~/.aws/credentials. I for one rotate my keys regulary using a tool. I think it would be wise to just support the default way of doing things.

kerem closed this issue

2026-03-04 01:45:57 +03:00

kerem commented

2026-03-04 01:45:58 +03:00

Author

Owner

@gaul commented on GitHub (Sep 19, 2018):

Agreed that s3fs should add this and a flag to choose non-default profiles for consistency with the AWS CLI. s3fs should continue to accept the current format. Historically s3fs used its own format since it predates the AWS CLI.

@gaul commented on GitHub (Sep 19, 2018): Agreed that s3fs should add this and a flag to choose non-default profiles for consistency with the AWS CLI. s3fs should continue to accept the current format. Historically s3fs used its own format since it predates the AWS CLI.

kerem referenced this issue

2026-03-04 02:01:03 +03:00

[PR #580] [MERGED] Enhanced bucket/path parameter check #1559