[GH-ISSUE #2349] No option to specify cert file (via command-line or credentials file) #1157

New issue

Open

opened 2026-03-04 01:51:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:51:48 +03:00

Owner

Originally created by @poppem on GitHub (Oct 16, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2349

Additional Information

Version of s3fs being used (`s3fs --version`)

V1.90 (commit:unknown)

Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`)

Version: 2.9.9-5ubuntu3

Kernel information (`uname -r`)

5.15.0-79-generic

GNU/Linux Distribution, if applicable (`cat /etc/os-release`)

Ubuntu 22.04.3 LTS

How to run s3fs, if applicable

n/a

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

n/a

Details about issue

The aws s3 client (as well as many other s3 clients) allow the user to specify the ca-bundle through a command-line option. This is not available in s3fs. For greater usability this needs to be added.
Additionally, since s3fs supports usage of the .aws/credentials file, the assumption was that s3fs would utilize the ca_bundle specified in the profile in this file but that is not the case. The certificate must be placed into the /etc/ssl/certs directory which the s3fs documentation does not state as required.

Originally created by @poppem on GitHub (Oct 16, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2349  ### Additional Information #### Version of s3fs being used (`s3fs --version`) V1.90 (commit:unknown) #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) Version: 2.9.9-5ubuntu3 #### Kernel information (`uname -r`) 5.15.0-79-generic #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) Ubuntu 22.04.3 LTS #### How to run s3fs, if applicable n/a #### s3fs syslog messages (`grep s3fs /var/log/syslog`, `journalctl | grep s3fs`, or `s3fs outputs`) n/a ### Details about issue The aws s3 client (as well as many other s3 clients) allow the user to specify the ca-bundle through a command-line option. This is not available in s3fs. For greater usability this needs to be added. Additionally, since s3fs supports usage of the .aws/credentials file, the assumption was that s3fs would utilize the ca_bundle specified in the profile in this file but that is not the case. The certificate must be placed into the /etc/ssl/certs directory which the s3fs documentation does not state as required.