[GH-ISSUE #619] SSE not working when executing s3fs command #352

New issue

Closed

opened 2026-03-04 01:44:39 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @calum-mcelhone on GitHub (Jun 22, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/619

Version of s3fs - 1.80

Details about issue

Hi Guys,

I am currently using s3fs to fuse a docker container directory to an S3 Bucket.

Files are syncing fine. The only issue i am running into is getting my files encrypted in my S3Bucket.

The command i am currently using to fuse is as follows:

sudo /usr/bin/s3fs lmb-enrollment-cust-bucket-${DEPLOY_REGION} /s3-share -o use_sse -o gid=$sftpGroupId,mp_umask=0002,allow_other -o umask=0002 -o iam_role=auto -o default_acl=private,retries=1

I am not getting any errors in my logs specifying encryption failed or the like. Its simply a case that the files sync without getting encrypted in the related S3Bucket.

As you can see i am passing the -o use_sse parameter so i would have expected the appropriate metadata to have been included in the PUT request to the S3Bucket.

If anyone has run into the same issue or can see clearly what the issue might be i would be interested to hear back from you.

Originally created by @calum-mcelhone on GitHub (Jun 22, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/619 - Version of s3fs - 1.80 #### Details about issue Hi Guys, I am currently using s3fs to fuse a docker container directory to an S3 Bucket. Files are syncing fine. The only issue i am running into is getting my files encrypted in my S3Bucket. The command i am currently using to fuse is as follows: sudo /usr/bin/s3fs lmb-enrollment-cust-bucket-${DEPLOY_REGION} /s3-share -o use_sse -o gid=$sftpGroupId,mp_umask=0002,allow_other -o umask=0002 -o iam_role=auto -o default_acl=private,retries=1 I am not getting any errors in my logs specifying encryption failed or the like. Its simply a case that the files sync without getting encrypted in the related S3Bucket. As you can see i am passing the -o use_sse parameter so i would have expected the appropriate metadata to have been included in the PUT request to the S3Bucket. If anyone has run into the same issue or can see clearly what the issue might be i would be interested to hear back from you.

kerem closed this issue

2026-03-04 01:44:40 +03:00

kerem commented

2026-03-04 01:44:40 +03:00

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Could you test with master? It includes a fix for #696 which may resolve your issue as well.

@gaul commented on GitHub (Apr 9, 2019): Could you test with master? It includes a fix for #696 which may resolve your issue as well.

kerem commented

2026-03-04 01:44:40 +03:00

Author

Owner

@gaul commented on GitHub (Apr 30, 2019):

Please reopen if you can reproduce these symptoms.

@gaul commented on GitHub (Apr 30, 2019): Please reopen if you can reproduce these symptoms.

kerem referenced this issue

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

[PR #352] [MERGED] Remove stat file cache dir if specified del_cache - #337 #1475