[GH-ISSUE #720] Environment Variables for Creds #411

New issue

Closed

opened 2026-03-04 01:45:17 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @jashaffe on GitHub (Feb 20, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/720

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.

Version of s3fs being used (s3fs --version)

_example: 1.83

Version of fuse being used (pkg-config --modversion fuse)

_example: 2.9.4

System information (uname -r)

_command result: 4.9.76-3.78.amzn1.x86_64

Distro (cat /etc/issue)

_command result: Amazon Linux AMI release 2017.09

s3fs command line used (if applicable)

/etc/fstab entry (if applicable):

s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

Details about issue

The instructions state that: setting the AWSACCESSKEYID and AWSSECRETACCESSKEY environment variables is an acceptable way of passing creds. When I do a man s3fs this doesnt show possible. I've noticed that older versions accept creds in arguments. Is the only way to write the API keys to file? I'd rather not write them disk for security.

Thanks!

Originally created by @jashaffe on GitHub (Feb 20, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/720 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ #### Version of s3fs being used (s3fs --version) _example: 1.83 #### Version of fuse being used (pkg-config --modversion fuse) _example: 2.9.4 #### System information (uname -r) _command result: 4.9.76-3.78.amzn1.x86_64 #### Distro (cat /etc/issue) _command result: Amazon Linux AMI release 2017.09 #### s3fs command line used (if applicable) ``` ``` #### /etc/fstab entry (if applicable): ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` ``` ### Details about issue The instructions state that: setting the AWSACCESSKEYID and AWSSECRETACCESSKEY environment variables is an acceptable way of passing creds. When I do a man s3fs this doesnt show possible. I've noticed that older versions accept creds in arguments. Is the only way to write the API keys to file? I'd rather not write them disk for security. Thanks!

kerem closed this issue

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

kerem commented

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

Author

Owner

@leblancexplores commented on GitHub (May 16, 2018):

@jashaffe a quick look at the .cpp it seems like it's still a thing? https://github.com/s3fs-fuse/s3fs-fuse/blob/master/src/s3fs.cpp#L4136

@leblancexplores commented on GitHub (May 16, 2018): @jashaffe a quick look at the .cpp it seems like it's still a thing? https://github.com/s3fs-fuse/s3fs-fuse/blob/master/src/s3fs.cpp#L4136

kerem commented

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

Author

Owner

@gaul commented on GitHub (Feb 2, 2019):

@jashaffe I confirmed that environment variables work. Could you share how you invoked s3fs?

@gaul commented on GitHub (Feb 2, 2019): @jashaffe I confirmed that environment variables work. Could you share how you invoked s3fs?

kerem commented

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

Author

Owner

@gaul commented on GitHub (Mar 17, 2019):

Works for me.

@gaul commented on GitHub (Mar 17, 2019): Works for me.

kerem referenced this issue

2026-03-04 01:54:15 +03:00

[PR #411] [MERGED] loading IAM role name automatically(iam_role option) - #387 #1496