[GH-ISSUE #1258] Unable to write files inside the bucket mounted #675

New issue

Open

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

kerem commented

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

Owner

Originally created by @mrcomac on GitHub (Mar 29, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1258

Update

when I use "aws s3 list" from instance and using the credentials inside passwd-s3fs I can list, create, delete buckets..
but when I use s3fs command I get the error:

Mar 30 14:14:29 ip-172-31-42-115 s3fs[4399]: s3fs.cpp:s3fs_check_service(3883): Failed to connect by sigv4, so retry to connect by signature version 2.
Mar 30 14:14:29 ip-172-31-42-115 s3fs[4399]: s3fs.cpp:s3fs_check_service(3898): invalid credentials(host=https://s3.amazonaws.com) - result of checking service.

Additional Information

s3fs installed using:
sudo amazon-linux-extras install epel -y
sudo yum install s3fs-fuse -y

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.86 (commit:unknown) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

s3fs command line used, if applicable

I tried these commands

sudo s3fs my-bucket-name -o allow_other /mnt/test
sudo s3fs my-bucket-name -o use_cache=/tmp -o allow_other -o multireq_max=5 /mnt/test

/etc/fstab entry, if applicable

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

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

Mar 29 10:56:44 ip-10-0-0-227 s3fs[12990]: init v1.86(commit:unknown) with OpenSSL
Mar 29 11:01:23 ip-10-0-0-227 s3fs[13060]: init v1.86(commit:unknown) with OpenSSL
Mar 29 11:07:20 ip-10-0-0-227 s3fs[13105]: init v1.86(commit:unknown) with OpenSSL
Mar 29 11:09:45 ip-10-0-0-227 s3fs[13139]: init v1.86(commit:unknown) with OpenSSL
Mar 29 11:11:47 ip-10-0-0-227 s3fs[13189]: init v1.86(commit:unknown) with OpenSSL
Mar 29 11:13:20 ip-10-0-0-227 s3fs[13207]: init v1.86(commit:unknown) with OpenSSL

Details about issue

I created user with AmazonS3FullAccess policy permission (Programmatic access user)
I put credentials in /etc/passwd-s3fs
I can mount the bucket
I can read files from the bucket inside the instance
I can't write data inside the bucket from the instance (the mount point is read-only)

When I try test write permission using touch to a exist file:
sudo touch /mnt/test/README.md
touch: cannot touch '/mnt/test/README.md': Permission denied

Originally created by @mrcomac on GitHub (Mar 29, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1258 ### Update when I use "aws s3 list" from instance and using the credentials inside passwd-s3fs I can list, create, delete buckets.. but when I use s3fs command I get the error: ``` Mar 30 14:14:29 ip-172-31-42-115 s3fs[4399]: s3fs.cpp:s3fs_check_service(3883): Failed to connect by sigv4, so retry to connect by signature version 2. Mar 30 14:14:29 ip-172-31-42-115 s3fs[4399]: s3fs.cpp:s3fs_check_service(3898): invalid credentials(host=https://s3.amazonaws.com) - result of checking service. ``` ### Additional Information s3fs installed using: sudo amazon-linux-extras install epel -y sudo yum install s3fs-fuse -y #### Version of s3fs being used (s3fs --version) Amazon Simple Storage Service File System V1.86 (commit:unknown) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. #### s3fs command line used, if applicable I tried these commands ``` sudo s3fs my-bucket-name -o allow_other /mnt/test sudo s3fs my-bucket-name -o use_cache=/tmp -o allow_other -o multireq_max=5 /mnt/test ``` #### /etc/fstab entry, if applicable ``` ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` Mar 29 10:56:44 ip-10-0-0-227 s3fs[12990]: init v1.86(commit:unknown) with OpenSSL Mar 29 11:01:23 ip-10-0-0-227 s3fs[13060]: init v1.86(commit:unknown) with OpenSSL Mar 29 11:07:20 ip-10-0-0-227 s3fs[13105]: init v1.86(commit:unknown) with OpenSSL Mar 29 11:09:45 ip-10-0-0-227 s3fs[13139]: init v1.86(commit:unknown) with OpenSSL Mar 29 11:11:47 ip-10-0-0-227 s3fs[13189]: init v1.86(commit:unknown) with OpenSSL Mar 29 11:13:20 ip-10-0-0-227 s3fs[13207]: init v1.86(commit:unknown) with OpenSSL ``` ### Details about issue 1. I created user with AmazonS3FullAccess policy permission (Programmatic access user) 2. I put credentials in /etc/passwd-s3fs 3. I can mount the bucket 4. I can read files from the bucket inside the instance 5. I can't write data inside the bucket from the instance (the mount point is read-only) When I try test write permission using touch to a exist file: `sudo touch /mnt/test/README.md` `touch: cannot touch '/mnt/test/README.md': Permission denied`