[GH-ISSUE #1708] AWSACCESSKEYID vs AWS_ACCESS_KEY_ID #881

New issue

Closed

opened 2026-03-04 01:49:38 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:49:38 +03:00

Owner

Originally created by @CarstenGrohmann on GitHub (Jun 30, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1708

The environment variables for an access key, secret key, and session token differ between s3fs and aws cli.
In s3fs, these variables are in uppercase but without underscore, and aws cli uses the same naming but with underscore. Is this intentional?

github.com/s3fs-fuse/s3fs-fuse@487df27008/src/s3fs.cpp (L3992-L3994)
AWS reference: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html#envvars-set

If this is not intended, then I can contribute a PR.

Originally created by @CarstenGrohmann on GitHub (Jun 30, 2021). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1708 The environment variables for an access key, secret key, and session token differ between s3fs and aws cli. In s3fs, these variables are in uppercase but without underscore, and aws cli uses the same naming but with underscore. Is this intentional? https://github.com/s3fs-fuse/s3fs-fuse/blob/487df2700842c0a74e6314b898d726ff57a55589/src/s3fs.cpp#L3992-L3994 AWS reference: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html#envvars-set If this is not intended, then I can contribute a PR.

kerem

2026-03-04 01:49:38 +03:00

closed this issue
added the
help wanted
label

kerem commented

2026-03-04 01:49:39 +03:00

Author

Owner

@gaul commented on GitHub (Jul 1, 2021):

s3fs (2007) predates the AWS CLI (2012) so it was not our intention but their choice (although I prefer their choice). AWS CLI is likely more popular and thus s3fs should align with their choices to reduce user friction. s3fs should accept both variants so it retains backwards compatibility for our users. We can change the s3fs documentation to only mention the AWS style though.

@gaul commented on GitHub (Jul 1, 2021): s3fs (2007) predates the AWS CLI (2012) so it was not our intention but their choice (although I prefer their choice). AWS CLI is likely more popular and thus s3fs should align with their choices to reduce user friction. s3fs should accept both variants so it retains backwards compatibility for our users. We can change the s3fs documentation to only mention the AWS style though.

kerem commented

2026-03-04 01:49:39 +03:00

Author

Owner

@CarstenGrohmann commented on GitHub (Jul 1, 2021):

ok, I'll create a PR

@CarstenGrohmann commented on GitHub (Jul 1, 2021): ok, I'll create a PR