[GH-ISSUE #2338] I can't mount an s3 bucket (token session) #1153

New issue

Closed

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

kerem commented

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

Owner

Originally created by @braxtoon-hash on GitHub (Oct 4, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2338

Version of s3fs being used

Amazon Simple Storage Service File System V1.90 (commit:unknown) with GnuTLS(gcrypt)

Details about issue

I'm on ubuntu and i'm trying to mount an s3 bucket with this command:
sudo s3fs <bucket> /home/<name>/buckets3/ -o passwd_file=aws -o url=https://s3.amazonaws.com -o use_session_token -o endpoint=eu-west-1 -f
With the keys specified in the aws file, and the session token + keys in /.aws/credentials
But I get these error messages
2023-10-04T14:07:30.632Z [INF] curl.cpp:InitMimeType(434): Loaded mime information from /etc/mime.types
2023-10-04T14:07:30.633Z [INF] s3fs.cpp:s3fs_init(3382): init v1.90(commit:unknown) with GnuTLS(gcrypt)
2023-10-04T14:07:30.737Z [CRT] s3fs.cpp:s3fs_check_service(3575): Failed to connect by sigv4, so retry to connect by signature version 2.
2023-10-04T14:07:30.760Z [CRT] s3fs.cpp:s3fs_check_service(3590): invalid credentials(host=https://s3.amazonaws.com) - result of checking service.`
Any ideas why ?

Originally created by @braxtoon-hash on GitHub (Oct 4, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2338 #### Version of s3fs being used Amazon Simple Storage Service File System V1.90 (commit:unknown) with GnuTLS(gcrypt) ### Details about issue I'm on ubuntu and i'm trying to mount an s3 bucket with this command: `sudo s3fs <bucket> /home/<name>/buckets3/ -o passwd_file=aws -o url=https://s3.amazonaws.com -o use_session_token -o endpoint=eu-west-1 -f` With the keys specified in the aws file, and the session token + keys in /.aws/credentials But I get these error messages `2023-10-04T14:07:30.632Z [INF] curl.cpp:InitMimeType(434): Loaded mime information from /etc/mime.types` `2023-10-04T14:07:30.633Z [INF] s3fs.cpp:s3fs_init(3382): init v1.90(commit:unknown) with GnuTLS(gcrypt)` `2023-10-04T14:07:30.737Z [CRT] s3fs.cpp:s3fs_check_service(3575): Failed to connect by sigv4, so retry to connect by signature version 2.` `2023-10-04T14:07:30.760Z [CRT] s3fs.cpp:s3fs_check_service(3590): invalid credentials(host=https://s3.amazonaws.com) - result of checking service`.` Any ideas why ?

kerem closed this issue

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

kerem commented

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

Author

Owner

@rohitsanj commented on GitHub (Oct 13, 2023):

Hey @braxtoon-hash, we're seeing a similar error. Were you able to figure out what the fix was?

@rohitsanj commented on GitHub (Oct 13, 2023): Hey @braxtoon-hash, we're seeing a similar error. Were you able to figure out what the fix was?

kerem commented

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

Author

Owner

@braxtoon-hash commented on GitHub (Nov 14, 2023):

Hey @braxtoon-hash, we're seeing a similar error. Were you able to figure out what the fix was?

Hey, sorry to reply so late and no I haven't found a viable solution, only sometimes it works sometimes it doesn't, I have no way of knowing why, I've tried lots of things. What seems to work best is to use IAM profiles with -o profile=name, with the keys in .aws/credentials.
If you've found a solution I'd be glad to know it.
Here is the command I use :
sudo s3fs bucket /home/XXX -o profile=YYY -o url="https://s3-eu-west-1.amazonaws.com" -o endpoint=eu-west-1 -o use_sse

@braxtoon-hash commented on GitHub (Nov 14, 2023): > Hey @braxtoon-hash, we're seeing a similar error. Were you able to figure out what the fix was? Hey, sorry to reply so late and no I haven't found a viable solution, only sometimes it works sometimes it doesn't, I have no way of knowing why, I've tried lots of things. What seems to work best is to use IAM profiles with -o profile=name, with the keys in .aws/credentials. If you've found a solution I'd be glad to know it. Here is the command I use : `sudo s3fs bucket /home/XXX -o profile=YYY -o url="https://s3-eu-west-1.amazonaws.com" -o endpoint=eu-west-1 -o use_sse`