[GH-ISSUE #401] Not sure which how credentials defined #213

New issue

Closed

opened 2026-03-04 01:43:17 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:43:17 +03:00

Owner

Originally created by @wytcld on GitHub (Apr 20, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/401

I'm getting "s3fs: could not determine how to establish security credentials" when the file I'm point to contains the email of the account owner plus password for that account. This is where the S3 container has had that email added for permission. I'd rather give permission based on a IAM user assignment, but don't see those in what's available for S3. Can someone please give a definition or example of which credentials should work here?

Originally created by @wytcld on GitHub (Apr 20, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/401 I'm getting "s3fs: could not determine how to establish security credentials" when the file I'm point to contains the email of the account owner plus password for that account. This is where the S3 container has had that email added for permission. I'd rather give permission based on a IAM user assignment, but don't see those in what's available for S3. Can someone please give a definition or example of which credentials should work here?

kerem closed this issue

2026-03-04 01:43:18 +03:00

kerem commented

2026-03-04 01:43:18 +03:00

Author

Owner

@wytcld commented on GitHub (Apr 20, 2016):

Tried the access key and secret key for a user account, and still got:

s3fs: could not determine how to establish security credentials.

@wytcld commented on GitHub (Apr 20, 2016): Tried the access key and secret key for a user account, and still got: s3fs: could not determine how to establish security credentials.

kerem commented

2026-03-04 01:43:18 +03:00

Author

Owner

@wytcld commented on GitHub (Apr 20, 2016):

Same if I create a new access key for the root user. Starting to think that "could not determine" error is at some other level.

@wytcld commented on GitHub (Apr 20, 2016): Same if I create a new access key for the root user. Starting to think that "could not determine" error is at some other level.

kerem commented

2026-03-04 01:43:19 +03:00

Author

Owner

@wytcld commented on GitHub (Apr 20, 2016):

Connection works if credentials put in /etc/passwd-s3fs. Evidently using arbitrary files elsewhere is broken. It does then complain:

s3fs.cpp:s3fs_check_service(3715): Could not connect wrong region us-east-1, so retry to connect region us-west-2.

... which is strange since the VM mounting it is in us-west-2, too.

@wytcld commented on GitHub (Apr 20, 2016): Connection works if credentials put in /etc/passwd-s3fs. Evidently using arbitrary files elsewhere is broken. It does then complain: s3fs.cpp:s3fs_check_service(3715): Could not connect wrong region us-east-1, so retry to connect region us-west-2. ... which is strange since the VM mounting it is in us-west-2, too.

kerem commented

2026-03-04 01:43:19 +03:00

Author

Owner

@wytcld commented on GitHub (Apr 20, 2016):

Ah my mistake, "passwd_file=" has to be explicitly there. I had thought that was more a label on the example. Misread, for sure.

@wytcld commented on GitHub (Apr 20, 2016): Ah my mistake, "passwd_file=" has to be explicitly there. I had thought that was more a label on the example. Misread, for sure.

kerem referenced this issue

2026-03-04 01:53:45 +03:00

[PR #213] [MERGED] Parse ETag from copy multipart correctly #1400