s3fs Input/output error

Question

I'm trying to set up a backup system with s3fs and the Amazon S3 service. I followed this this guide and this guide.

Tailing /var/log/messages I get:

Aug 28 13:37:46 server s3fs:###response=403

I already tried creating the authentication file /etc/passwd-s3fs and setting the access and private key, passing it through the command line. I checked several times the credentials and I used it with s3fox, and it is working.

I also have set the time of the machine (with the date command) to be the same as the Amazon S3 servers (I got the time of the S3 server uploading a file with the file manager).

Not only does rsync not work, commands like ls or cp in /mnt/s3 didn't work also.

Solution 1

You can actually store the credentials in two places. System level or user level. Not clear from your question where you have things set. Each requires different permission settings.

For system level placement in /etc/passwd-s3fs the permissions should be 640. So adjust with chmod like so if that is not the case:

sudo chmod 640 /etc/passwd-s3fs

For user level placement in ~/.passwd-s3fs the permissions should be 600. So adjust with chmod like so if that is not the case:

chmod 600 ~/.passwd-s3fs

Also, the contents of each of those files should follow the fairly simple format of AccessKey:SuperSecretKey with nothing else needed. AccessKey on one side of the colon (:) ad the SuperSecretKey on the other side.

Solution 2

Hi some few times I also mount s3 bucket on linux. I noted the below link for this. Normal documentation miss an important note about permissions. So first you need to unmout the location then change permissions of both key and directory then mount again.

Your mount directory permission must be 777 and key file permission must be 600. Please check below documentation.

chmod 777 /mnt/dir/
chmod 600 ~/.passwd-s3fs

Mount AWS S3 bucket to Ubuntu file system

Hope this will help because I use that documentation many times on cloud.

Comments

[shadow_of__soul]

all of that has been checked, and it still didn't worked