starred/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00
Code Issues 305 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #2612] The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential (EC2 with IAM Role) #1247

New issue
Closed
opened 2026-03-04 01:52:32 +03:00 by kerem · 5 comments
kerem commented 2026-03-04 01:52:32 +03:00
Owner
Copy link

Originally created by @Cookieees on GitHub (Nov 16, 2024).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2612

Additional Information

Version of s3fs being used (s3fs --version)

V1.95 (commit:561ce1e)

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse or dpkg -s fuse)

> pkg-config --modversion fuse
2.9.9

Kernel information (uname -r)

6.8.0-1018-aws

GNU/Linux Distribution, if applicable (cat /etc/os-release)

PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

How to run s3fs, if applicable

[ x ] command line
[ ] /etc/fstab

s3fs my-bucket-name \
  -o use_path_request_style \
  -o url=http://s3-eu-central-1.amazonaws.com \
  -o endpoint=eu-central-1 \
  -o iam_role=auto \
  -o allow_other \
  -o uid=1000 \
  -o gid=1000 \
  -o dbglevel=debug \
  -o curldbg \
  -o no_check_certificate \
  -o retries=5 \
  /mnt/s3bucket

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

The part of Syslog output (grep s3fs) 
2024-11-16T12:17:17.874914+00:00 ip-10-0-18-158 s3fs[1706]: *   Trying 52.219.169.58:80...
2024-11-16T12:17:17.875063+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to my-bucket-name.s3-eu-central-1.amazonaws.com (52.219.169.58) port 80
2024-11-16T12:17:17.875315+00:00 ip-10-0-18-158 s3fs[1706]: > GET / HTTP/1.1
2024-11-16T12:17:17.875510+00:00 ip-10-0-18-158 s3fs[1706]: > Host: my-bucket-name.s3-eu-central-1.amazonaws.com
2024-11-16T12:17:17.875691+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL)
2024-11-16T12:17:17.875775+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */*
2024-11-16T12:17:17.876020+00:00 ip-10-0-18-158 s3fs[1706]: > Authorization: AWS4-HMAC-SHA256 Credential=/20241116/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=ba6499583ddf976aa04fef6a6108faf8f3866654a26f0e295502e95046ee41e0
2024-11-16T12:17:17.876144+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2024-11-16T12:17:17.876207+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-date: 20241116T121717Z
2024-11-16T12:17:17.876363+00:00 ip-10-0-18-158 s3fs[1706]: >
2024-11-16T12:17:17.876498+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 400 Bad Request
2024-11-16T12:17:17.876577+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-bucket-region: eu-central-1
2024-11-16T12:17:17.876674+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-request-id: 6K7RTXAKX81SN8GJ
2024-11-16T12:17:17.876783+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-id-2: zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM=
2024-11-16T12:17:17.877021+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: application/xml
2024-11-16T12:17:17.877070+00:00 ip-10-0-18-158 s3fs[1706]: < Transfer-Encoding: chunked
2024-11-16T12:17:17.877447+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT
2024-11-16T12:17:17.877488+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close
2024-11-16T12:17:17.877513+00:00 ip-10-0-18-158 s3fs[1706]: < Server: AmazonS3
2024-11-16T12:17:17.877707+00:00 ip-10-0-18-158 s3fs[1706]: <
2024-11-16T12:17:17.877787+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection
2024-11-16T12:17:17.877967+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2602): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential.</Message><RequestId>6K7RTXAKX81SN8GJ</RequestId><HostId>zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM=</HostId></Error>
2024-11-16T12:17:17.878091+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:CheckBucket(3790): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential.</Message><RequestId>6K7RTXAKX81SN8GJ</RequestId><HostId>zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM=</HostId></Error>
2024-11-16T12:17:17.878183+00:00 ip-10-0-18-158 s3fs[1706]: threadpoolman.cpp:Worker(132): The instruction function returned with something error code(-5).
2024-11-16T12:17:17.878329+00:00 ip-10-0-18-158 s3fs[1706]: s3fs_threadreqs.cpp:check_service_request(535): Await Check Service Request by error(-5) [path=/][support compat dir=false][force No SSE=false]
2024-11-16T12:17:17.878374+00:00 ip-10-0-18-158 s3fs[1706]:       Check Service Request [path=/][support compat dir=false][force No SSE=false]
2024-11-16T12:17:17.878572+00:00 ip-10-0-18-158 s3fs[1706]:       check a bucket path(/).
2024-11-16T12:17:17.878890+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect.
2024-11-16T12:17:17.878947+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities.
2024-11-16T12:17:17.878987+00:00 ip-10-0-18-158 s3fs[1706]:       URL is http://s3-eu-central-1.amazonaws.com/my-bucket-name/
2024-11-16T12:17:17.879024+00:00 ip-10-0-18-158 s3fs[1706]:       URL changed is http://my-bucket-name.s3-eu-central-1.amazonaws.com/
2024-11-16T12:17:17.879059+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://my-bucket-name.s3-eu-central-1.amazonaws.com/
2024-11-16T12:17:17.879083+00:00 ip-10-0-18-158 s3fs[1706]: IAM Access Token refreshing...
2024-11-16T12:17:17.879105+00:00 ip-10-0-18-158 s3fs[1706]:       [IAM role=ec2-s3-access-role]
2024-11-16T12:17:17.879127+00:00 ip-10-0-18-158 s3fs[1706]:       Get IAMv2 API Toekn Request directly [url=http://169.254.169.254/latest/api/token][token ttl=21600][ttl header=X-aws-ec2-metadata-token-ttl-seconds]
2024-11-16T12:17:17.879149+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect.
2024-11-16T12:17:17.879171+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities.
2024-11-16T12:17:17.879193+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://169.254.169.254/latest/api/token
2024-11-16T12:17:17.879216+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname 169.254.169.254 was found in DNS cache
2024-11-16T12:17:17.879242+00:00 ip-10-0-18-158 s3fs[1706]: *   Trying 169.254.169.254:80...
2024-11-16T12:17:17.879265+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to 169.254.169.254 (169.254.169.254) port 80
2024-11-16T12:17:17.879287+00:00 ip-10-0-18-158 s3fs[1706]: > PUT /latest/api/token HTTP/1.1
2024-11-16T12:17:17.879309+00:00 ip-10-0-18-158 s3fs[1706]: > Host: 169.254.169.254
2024-11-16T12:17:17.879330+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL)
2024-11-16T12:17:17.879353+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */*
2024-11-16T12:17:17.879375+00:00 ip-10-0-18-158 s3fs[1706]: > X-aws-ec2-metadata-token-ttl-seconds: 21600
2024-11-16T12:17:17.879397+00:00 ip-10-0-18-158 s3fs[1706]: > Content-Length: 0
2024-11-16T12:17:17.879419+00:00 ip-10-0-18-158 s3fs[1706]: >
2024-11-16T12:17:17.879419+00:00 ip-10-0-18-158 s3fs[1706]: >
2024-11-16T12:17:17.879967+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 200 OK
2024-11-16T12:17:17.880162+00:00 ip-10-0-18-158 s3fs[1706]: < X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600
2024-11-16T12:17:17.880279+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Length: 56
2024-11-16T12:17:17.880556+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT
2024-11-16T12:17:17.880615+00:00 ip-10-0-18-158 s3fs[1706]: < Server: EC2ws
2024-11-16T12:17:17.880688+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close
2024-11-16T12:17:17.880837+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: text/plain
2024-11-16T12:17:17.880968+00:00 ip-10-0-18-158 s3fs[1706]: <
2024-11-16T12:17:17.881095+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection
2024-11-16T12:17:17.881303+00:00 ip-10-0-18-158 s3fs[1706]:       HTTP response code 200
2024-11-16T12:17:17.881346+00:00 ip-10-0-18-158 s3fs[1706]:       Setting AWS IMDSv2 API token to AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA==
2024-11-16T12:17:17.881383+00:00 ip-10-0-18-158 s3fs[1706]:       Get IAM Credentials Request directly [url=http://169.254.169.254/latest/meta-data/iam/security-credentials/ec2-s3-access-role][iam token=AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA==][ibm secrect access key=]
2024-11-16T12:17:17.881582+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect.
2024-11-16T12:17:17.881607+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities.
2024-11-16T12:17:17.881630+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://169.254.169.254/latest/meta-data/iam/security-credentials/ec2-s3-access-role
2024-11-16T12:17:17.881658+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname 169.254.169.254 was found in DNS cache
2024-11-16T12:17:17.881681+00:00 ip-10-0-18-158 s3fs[1706]: *   Trying 169.254.169.254:80...
2024-11-16T12:17:17.881707+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to 169.254.169.254 (169.254.169.254) port 80
2024-11-16T12:17:17.881730+00:00 ip-10-0-18-158 s3fs[1706]: > GET /latest/meta-data/iam/security-credentials/ec2-s3-access-role HTTP/1.1
2024-11-16T12:17:17.881751+00:00 ip-10-0-18-158 s3fs[1706]: > Host: 169.254.169.254
2024-11-16T12:17:17.881773+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL)
2024-11-16T12:17:17.881795+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */*
2024-11-16T12:17:17.881816+00:00 ip-10-0-18-158 s3fs[1706]: > X-aws-ec2-metadata-token: AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA==
2024-11-16T12:17:17.881838+00:00 ip-10-0-18-158 s3fs[1706]: >
2024-11-16T12:17:17.881862+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 200 OK
2024-11-16T12:17:17.881883+00:00 ip-10-0-18-158 s3fs[1706]: < X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600
2024-11-16T12:17:17.881905+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: text/plain
2024-11-16T12:17:17.881928+00:00 ip-10-0-18-158 s3fs[1706]: < Accept-Ranges: none
2024-11-16T12:17:17.881949+00:00 ip-10-0-18-158 s3fs[1706]: < Last-Modified: Sat, 16 Nov 2024 11:28:33 GMT
2024-11-16T12:17:17.881975+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Length: 1598
2024-11-16T12:17:17.882000+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT
2024-11-16T12:17:17.882022+00:00 ip-10-0-18-158 s3fs[1706]: < Server: EC2ws
2024-11-16T12:17:17.882044+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close
2024-11-16T12:17:17.882065+00:00 ip-10-0-18-158 s3fs[1706]: <
2024-11-16T12:17:17.882087+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection
2024-11-16T12:17:17.882109+00:00 ip-10-0-18-158 s3fs[1706]:       HTTP response code 200
2024-11-16T12:17:17.882130+00:00 ip-10-0-18-158 s3fs[1706]: s3fs_cred.cpp:LoadIAMCredentials(450): Succeed to set IAM credentials
2024-11-16T12:17:17.882151+00:00 ip-10-0-18-158 s3fs[1706]: IAM Access Token refreshed
2024-11-16T12:17:17.882173+00:00 ip-10-0-18-158 s3fs[1706]:       computing signature [GET] [/] [] []
2024-11-16T12:17:17.882231+00:00 ip-10-0-18-158 s3fs[1706]:       url is http://s3-eu-central-1.amazonaws.com
2024-11-16T12:17:17.882258+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname my-bucket-name.s3-eu-central-1.amazonaws.com was found in DNS cache
2024-11-16T12:17:17.882283+00:00 ip-10-0-18-158 s3fs[1706]: *   Trying 52.219.169.58:80...
2024-11-16T12:17:17.882307+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to my-bucket-name.s3-eu-central-1.amazonaws.com (52.219.169.58) port 80
2024-11-16T12:17:17.882342+00:00 ip-10-0-18-158 s3fs[1706]: > GET / HTTP/1.1
2024-11-16T12:17:17.882364+00:00 ip-10-0-18-158 s3fs[1706]: > Host: my-bucket-name.s3-eu-central-1.amazonaws.com
2024-11-16T12:17:17.882387+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL)
2024-11-16T12:17:17.882409+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */*
2024-11-16T12:17:17.883248+00:00 ip-10-0-18-158 s3fs[1706]: > Authorization: AWS4-HMAC-SHA256 Credential=/20241116/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=ba6499583ddf976aa04fef6a6108faf8f3866654a26f0e295502e95046ee41e0
2024-11-16T12:17:17.883336+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2024-11-16T12:17:17.883532+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-date: 20241116T121717Z
2024-11-16T12:17:17.883732+00:00 ip-10-0-18-158 s3fs[1706]: >
2024-11-16T12:17:17.883996+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 400 Bad Request
...

The main is:

The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential

Details about issue

I want to mount an s3 bucket to my EC2 instance in AWS. But it seems that s3fs is somehow not performing requests to s3 correctly.

I have checked access to the bucket from this instance using aws-cli, aws sdk (via a simple Python script)

import boto3

session = boto3.Session()
s3 = session.client('s3')

response = s3.list_objects_v2(Bucket='my-bucket-name')
print(response)

and also checked for credentials using curl -s http://169.254.169.254/latest/meta-data/iam/security-credentials/<role_name>.

All of this works.
In the end I even inserted AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY_KEY and AWS_SESSION_TOKEN into the environment variables with the values of the temporary credetials from the AWS SSO page. And s3fs successfully mounted the bucket and the mount worked, of course until the credetials expired.

I also tried specifying for the -o iam_role option in addition to the auto value the name of the actual IAM role - same result.
If I don't specify this option at all I get the s3fs: could not determine how to establish security credentials. error
Also I tried to use and not to use the option pathstyle - the result did not change.

But in the end, the same command specified at the beginning of the Issue, but without the iam_role option, with temporary creds in the environment variables - successfully performed the mount.

Is it possible to make s3fs work successfully with iam_role?

Originally created by @Cookieees on GitHub (Nov 16, 2024). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2612 <!-- -------------------------------------------------------------------------- The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all. Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD. --------------------------------------------------------------------------- --> ### Additional Information #### Version of s3fs being used (`s3fs --version`) <!-- example: V1.91 (commit:b19262a) --> ``` V1.95 (commit:561ce1e) ``` #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) <!-- example: 2.9.2 --> ``` > pkg-config --modversion fuse 2.9.9 ``` #### Kernel information (`uname -r`) <!-- example: 5.10.96-90.460.amzn2.x86_64 --> ``` 6.8.0-1018-aws ``` #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) <!-- command result --> ``` PRETTY_NAME="Ubuntu 24.04.1 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.1 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo ``` #### How to run s3fs, if applicable <!-- Describe the s3fs "command line" or "/etc/fstab" entry used. --> [ x ] command line [ ] /etc/fstab <!-- Executed command line or /etc/fastab entry --> ``` s3fs my-bucket-name \ -o use_path_request_style \ -o url=http://s3-eu-central-1.amazonaws.com \ -o endpoint=eu-central-1 \ -o iam_role=auto \ -o allow_other \ -o uid=1000 \ -o gid=1000 \ -o dbglevel=debug \ -o curldbg \ -o no_check_certificate \ -o retries=5 \ /mnt/s3bucket ``` #### 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. --> <details> <summary>The part of Syslog output (grep s3fs)</summary> ``` 2024-11-16T12:17:17.874914+00:00 ip-10-0-18-158 s3fs[1706]: * Trying 52.219.169.58:80... 2024-11-16T12:17:17.875063+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to my-bucket-name.s3-eu-central-1.amazonaws.com (52.219.169.58) port 80 2024-11-16T12:17:17.875315+00:00 ip-10-0-18-158 s3fs[1706]: > GET / HTTP/1.1 2024-11-16T12:17:17.875510+00:00 ip-10-0-18-158 s3fs[1706]: > Host: my-bucket-name.s3-eu-central-1.amazonaws.com 2024-11-16T12:17:17.875691+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL) 2024-11-16T12:17:17.875775+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */* 2024-11-16T12:17:17.876020+00:00 ip-10-0-18-158 s3fs[1706]: > Authorization: AWS4-HMAC-SHA256 Credential=/20241116/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=ba6499583ddf976aa04fef6a6108faf8f3866654a26f0e295502e95046ee41e0 2024-11-16T12:17:17.876144+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2024-11-16T12:17:17.876207+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-date: 20241116T121717Z 2024-11-16T12:17:17.876363+00:00 ip-10-0-18-158 s3fs[1706]: > 2024-11-16T12:17:17.876498+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 400 Bad Request 2024-11-16T12:17:17.876577+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-bucket-region: eu-central-1 2024-11-16T12:17:17.876674+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-request-id: 6K7RTXAKX81SN8GJ 2024-11-16T12:17:17.876783+00:00 ip-10-0-18-158 s3fs[1706]: < x-amz-id-2: zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM= 2024-11-16T12:17:17.877021+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: application/xml 2024-11-16T12:17:17.877070+00:00 ip-10-0-18-158 s3fs[1706]: < Transfer-Encoding: chunked 2024-11-16T12:17:17.877447+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT 2024-11-16T12:17:17.877488+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close 2024-11-16T12:17:17.877513+00:00 ip-10-0-18-158 s3fs[1706]: < Server: AmazonS3 2024-11-16T12:17:17.877707+00:00 ip-10-0-18-158 s3fs[1706]: < 2024-11-16T12:17:17.877787+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection 2024-11-16T12:17:17.877967+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2602): HTTP response code 400, returning EIO. Body Text: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential.</Message><RequestId>6K7RTXAKX81SN8GJ</RequestId><HostId>zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM=</HostId></Error> 2024-11-16T12:17:17.878091+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:CheckBucket(3790): Check bucket failed, S3 response: <?xml version="1.0" encoding="UTF-8"?>#012<Error><Code>AuthorizationHeaderMalformed</Code><Message>The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential.</Message><RequestId>6K7RTXAKX81SN8GJ</RequestId><HostId>zIWHDf64ys8rZ+WVj/CpUVfqwVIscJ34cZM0w+Ka5XLePi6zDBtRU+I1LucCAE2AcmHJDsOKvRM=</HostId></Error> 2024-11-16T12:17:17.878183+00:00 ip-10-0-18-158 s3fs[1706]: threadpoolman.cpp:Worker(132): The instruction function returned with something error code(-5). 2024-11-16T12:17:17.878329+00:00 ip-10-0-18-158 s3fs[1706]: s3fs_threadreqs.cpp:check_service_request(535): Await Check Service Request by error(-5) [path=/][support compat dir=false][force No SSE=false] 2024-11-16T12:17:17.878374+00:00 ip-10-0-18-158 s3fs[1706]: Check Service Request [path=/][support compat dir=false][force No SSE=false] 2024-11-16T12:17:17.878572+00:00 ip-10-0-18-158 s3fs[1706]: check a bucket path(/). 2024-11-16T12:17:17.878890+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect. 2024-11-16T12:17:17.878947+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities. 2024-11-16T12:17:17.878987+00:00 ip-10-0-18-158 s3fs[1706]: URL is http://s3-eu-central-1.amazonaws.com/my-bucket-name/ 2024-11-16T12:17:17.879024+00:00 ip-10-0-18-158 s3fs[1706]: URL changed is http://my-bucket-name.s3-eu-central-1.amazonaws.com/ 2024-11-16T12:17:17.879059+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://my-bucket-name.s3-eu-central-1.amazonaws.com/ 2024-11-16T12:17:17.879083+00:00 ip-10-0-18-158 s3fs[1706]: IAM Access Token refreshing... 2024-11-16T12:17:17.879105+00:00 ip-10-0-18-158 s3fs[1706]: [IAM role=ec2-s3-access-role] 2024-11-16T12:17:17.879127+00:00 ip-10-0-18-158 s3fs[1706]: Get IAMv2 API Toekn Request directly [url=http://169.254.169.254/latest/api/token][token ttl=21600][ttl header=X-aws-ec2-metadata-token-ttl-seconds] 2024-11-16T12:17:17.879149+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect. 2024-11-16T12:17:17.879171+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities. 2024-11-16T12:17:17.879193+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://169.254.169.254/latest/api/token 2024-11-16T12:17:17.879216+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname 169.254.169.254 was found in DNS cache 2024-11-16T12:17:17.879242+00:00 ip-10-0-18-158 s3fs[1706]: * Trying 169.254.169.254:80... 2024-11-16T12:17:17.879265+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to 169.254.169.254 (169.254.169.254) port 80 2024-11-16T12:17:17.879287+00:00 ip-10-0-18-158 s3fs[1706]: > PUT /latest/api/token HTTP/1.1 2024-11-16T12:17:17.879309+00:00 ip-10-0-18-158 s3fs[1706]: > Host: 169.254.169.254 2024-11-16T12:17:17.879330+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL) 2024-11-16T12:17:17.879353+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */* 2024-11-16T12:17:17.879375+00:00 ip-10-0-18-158 s3fs[1706]: > X-aws-ec2-metadata-token-ttl-seconds: 21600 2024-11-16T12:17:17.879397+00:00 ip-10-0-18-158 s3fs[1706]: > Content-Length: 0 2024-11-16T12:17:17.879419+00:00 ip-10-0-18-158 s3fs[1706]: > 2024-11-16T12:17:17.879419+00:00 ip-10-0-18-158 s3fs[1706]: > 2024-11-16T12:17:17.879967+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 200 OK 2024-11-16T12:17:17.880162+00:00 ip-10-0-18-158 s3fs[1706]: < X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600 2024-11-16T12:17:17.880279+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Length: 56 2024-11-16T12:17:17.880556+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT 2024-11-16T12:17:17.880615+00:00 ip-10-0-18-158 s3fs[1706]: < Server: EC2ws 2024-11-16T12:17:17.880688+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close 2024-11-16T12:17:17.880837+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: text/plain 2024-11-16T12:17:17.880968+00:00 ip-10-0-18-158 s3fs[1706]: < 2024-11-16T12:17:17.881095+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection 2024-11-16T12:17:17.881303+00:00 ip-10-0-18-158 s3fs[1706]: HTTP response code 200 2024-11-16T12:17:17.881346+00:00 ip-10-0-18-158 s3fs[1706]: Setting AWS IMDSv2 API token to AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA== 2024-11-16T12:17:17.881383+00:00 ip-10-0-18-158 s3fs[1706]: Get IAM Credentials Request directly [url=http://169.254.169.254/latest/meta-data/iam/security-credentials/ec2-s3-access-role][iam token=AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA==][ibm secrect access key=] 2024-11-16T12:17:17.881582+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2041): 'no_check_certificate' option in effect. 2024-11-16T12:17:17.881607+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:ResetHandle(2042): The server certificate won't be checked against the available certificate authorities. 2024-11-16T12:17:17.881630+00:00 ip-10-0-18-158 s3fs[1706]: curl.cpp:RequestPerform(2523): connecting to URL http://169.254.169.254/latest/meta-data/iam/security-credentials/ec2-s3-access-role 2024-11-16T12:17:17.881658+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname 169.254.169.254 was found in DNS cache 2024-11-16T12:17:17.881681+00:00 ip-10-0-18-158 s3fs[1706]: * Trying 169.254.169.254:80... 2024-11-16T12:17:17.881707+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to 169.254.169.254 (169.254.169.254) port 80 2024-11-16T12:17:17.881730+00:00 ip-10-0-18-158 s3fs[1706]: > GET /latest/meta-data/iam/security-credentials/ec2-s3-access-role HTTP/1.1 2024-11-16T12:17:17.881751+00:00 ip-10-0-18-158 s3fs[1706]: > Host: 169.254.169.254 2024-11-16T12:17:17.881773+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL) 2024-11-16T12:17:17.881795+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */* 2024-11-16T12:17:17.881816+00:00 ip-10-0-18-158 s3fs[1706]: > X-aws-ec2-metadata-token: AQAEAMj0RM0Dw1bQXHyPq7KULu73YqTZgkA5EB2SXdrZLlRrKSEmIA== 2024-11-16T12:17:17.881838+00:00 ip-10-0-18-158 s3fs[1706]: > 2024-11-16T12:17:17.881862+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 200 OK 2024-11-16T12:17:17.881883+00:00 ip-10-0-18-158 s3fs[1706]: < X-Aws-Ec2-Metadata-Token-Ttl-Seconds: 21600 2024-11-16T12:17:17.881905+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Type: text/plain 2024-11-16T12:17:17.881928+00:00 ip-10-0-18-158 s3fs[1706]: < Accept-Ranges: none 2024-11-16T12:17:17.881949+00:00 ip-10-0-18-158 s3fs[1706]: < Last-Modified: Sat, 16 Nov 2024 11:28:33 GMT 2024-11-16T12:17:17.881975+00:00 ip-10-0-18-158 s3fs[1706]: < Content-Length: 1598 2024-11-16T12:17:17.882000+00:00 ip-10-0-18-158 s3fs[1706]: < Date: Sat, 16 Nov 2024 12:17:17 GMT 2024-11-16T12:17:17.882022+00:00 ip-10-0-18-158 s3fs[1706]: < Server: EC2ws 2024-11-16T12:17:17.882044+00:00 ip-10-0-18-158 s3fs[1706]: < Connection: close 2024-11-16T12:17:17.882065+00:00 ip-10-0-18-158 s3fs[1706]: < 2024-11-16T12:17:17.882087+00:00 ip-10-0-18-158 s3fs[1706]: * Closing connection 2024-11-16T12:17:17.882109+00:00 ip-10-0-18-158 s3fs[1706]: HTTP response code 200 2024-11-16T12:17:17.882130+00:00 ip-10-0-18-158 s3fs[1706]: s3fs_cred.cpp:LoadIAMCredentials(450): Succeed to set IAM credentials 2024-11-16T12:17:17.882151+00:00 ip-10-0-18-158 s3fs[1706]: IAM Access Token refreshed 2024-11-16T12:17:17.882173+00:00 ip-10-0-18-158 s3fs[1706]: computing signature [GET] [/] [] [] 2024-11-16T12:17:17.882231+00:00 ip-10-0-18-158 s3fs[1706]: url is http://s3-eu-central-1.amazonaws.com 2024-11-16T12:17:17.882258+00:00 ip-10-0-18-158 s3fs[1706]: * Hostname my-bucket-name.s3-eu-central-1.amazonaws.com was found in DNS cache 2024-11-16T12:17:17.882283+00:00 ip-10-0-18-158 s3fs[1706]: * Trying 52.219.169.58:80... 2024-11-16T12:17:17.882307+00:00 ip-10-0-18-158 s3fs[1706]: * Connected to my-bucket-name.s3-eu-central-1.amazonaws.com (52.219.169.58) port 80 2024-11-16T12:17:17.882342+00:00 ip-10-0-18-158 s3fs[1706]: > GET / HTTP/1.1 2024-11-16T12:17:17.882364+00:00 ip-10-0-18-158 s3fs[1706]: > Host: my-bucket-name.s3-eu-central-1.amazonaws.com 2024-11-16T12:17:17.882387+00:00 ip-10-0-18-158 s3fs[1706]: > User-Agent: s3fs/1.95 (commit hash (commit:a1e47bc +untracked files); OpenSSL) 2024-11-16T12:17:17.882409+00:00 ip-10-0-18-158 s3fs[1706]: > Accept: */* 2024-11-16T12:17:17.883248+00:00 ip-10-0-18-158 s3fs[1706]: > Authorization: AWS4-HMAC-SHA256 Credential=/20241116/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=ba6499583ddf976aa04fef6a6108faf8f3866654a26f0e295502e95046ee41e0 2024-11-16T12:17:17.883336+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 2024-11-16T12:17:17.883532+00:00 ip-10-0-18-158 s3fs[1706]: > x-amz-date: 20241116T121717Z 2024-11-16T12:17:17.883732+00:00 ip-10-0-18-158 s3fs[1706]: > 2024-11-16T12:17:17.883996+00:00 ip-10-0-18-158 s3fs[1706]: < HTTP/1.1 400 Bad Request ... ``` </details> The main is: ``` The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential ``` ### Details about issue I want to mount an s3 bucket to my EC2 instance in AWS. But it seems that s3fs is somehow not performing requests to s3 correctly. I have checked access to the bucket from this instance using aws-cli, aws sdk (via a simple Python script) ```python import boto3 session = boto3.Session() s3 = session.client('s3') response = s3.list_objects_v2(Bucket='my-bucket-name') print(response) ``` and also checked for credentials using `curl -s http://169.254.169.254/latest/meta-data/iam/security-credentials/<role_name>`. All of this works. In the end I even inserted AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY_KEY and AWS_SESSION_TOKEN into the environment variables with the values of the temporary credetials from the AWS SSO page. And s3fs successfully mounted the bucket and the mount worked, of course until the credetials expired. I also tried specifying for the `-o iam_role` option in addition to the `auto` value the name of the actual IAM role - same result. If I don't specify this option at all I get the `s3fs: could not determine how to establish security credentials.` error Also I tried to use and not to use the option `pathstyle` - the result did not change. But in the end, the same command specified at the beginning of the Issue, but without the iam_role option, with temporary creds in the environment variables - successfully performed the mount. Is it possible to make s3fs work successfully with iam_role?
kerem 2026-03-04 01:52:32 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-04 01:52:33 +03:00
Author
Owner
Copy link

@ScottSorrentino commented on GitHub (Nov 19, 2024):

I can confirm running into this same issue with the latest code. Seeing the same "malformed response / non-empty AKID must be provided" messages when running with debugging enabled. No change in behavior when using IMDSv1 or IMDSv2 on an EC2 instance with an attached Instance Profile; both fail to access the bucket.

Looks like the issue may have been introduced as part of the refactor to introduce s3fs_threadreqs.cpp in efc23316e9.

<!-- gh-comment-id:2486722173 --> @ScottSorrentino commented on GitHub (Nov 19, 2024): I can confirm running into this same issue with the latest code. Seeing the same "malformed response / non-empty AKID must be provided" messages when running with debugging enabled. No change in behavior when using IMDSv1 or IMDSv2 on an EC2 instance with an attached Instance Profile; both fail to access the bucket. Looks like the issue may have been introduced as part of the refactor to introduce `s3fs_threadreqs.cpp` in efc23316e9f5270e7821fe220dc5d2883f93c9ac.
kerem commented 2026-03-04 01:52:33 +03:00
Author
Owner
Copy link

@nikovolkov commented on GitHub (Nov 21, 2024):

I can confirm running into this same issue with the latest code. Seeing the same "malformed response / non-empty AKID must be provided" messages when running with debugging enabled. No change in behavior when using IMDSv1 or IMDSv2 on an EC2 instance with an attached Instance Profile; both fail to access the bucket.

Looks like the issue may have been introduced as part of the refactor to introduce s3fs_threadreqs.cpp in efc2331.

faced same issue

<!-- gh-comment-id:2491100536 --> @nikovolkov commented on GitHub (Nov 21, 2024): > I can confirm running into this same issue with the latest code. Seeing the same "malformed response / non-empty AKID must be provided" messages when running with debugging enabled. No change in behavior when using IMDSv1 or IMDSv2 on an EC2 instance with an attached Instance Profile; both fail to access the bucket. > > Looks like the issue may have been introduced as part of the refactor to introduce `s3fs_threadreqs.cpp` in [efc2331](https://github.com/s3fs-fuse/s3fs-fuse/commit/efc23316e9f5270e7821fe220dc5d2883f93c9ac). faced same issue
kerem commented 2026-03-04 01:52:33 +03:00
Author
Owner
Copy link

@mvisser-nhb commented on GitHub (Jan 8, 2025):

I rolled back to v1.94 and using iam_role=auto works again.

Script I use to mount my s3 bucket, where I added checking out to v1.94, basically pinning it to that version


# Variables
BUCKET_NAME="my-app-filestorage"
MOUNT_POINT="/mnt/storage"
NGINX_USER="nginx"
NGINX_GROUP="nginx"

# Ensure the mount point directory exists
if [ ! -d "$MOUNT_POINT" ]; then
  echo "Creating mount point directory: $MOUNT_POINT"
  sudo mkdir -p "$MOUNT_POINT"
fi

# Install necessary dependencies and tools
yum install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel -y
git clone https://github.com/s3fs-fuse/s3fs-fuse.git
cd s3fs-fuse
git checkout v1.94
./autogen.sh
./configure --prefix=/usr --with-openssl
make
make install

## Mount the S3 bucket with specific user and group ownership (nginx user)
#s3fs $BUCKET_NAME $MOUNT_POINT -o iam_role=auto,uid=$(id -u $NGINX_USER),gid=$(id -g $NGINX_GROUP)

# Add the entry to /etc/fstab for persistence
FSTAB_ENTRY="s3fs#$BUCKET_NAME $MOUNT_POINT fuse _netdev,iam_role=auto,uid=$(id -u $NGINX_USER),gid=$(id -g $NGINX_GROUP),umask=0022,allow_other,nosuid,nodev 0 0"

# Check if the entry already exists in /etc/fstab
if ! grep -q "$FSTAB_ENTRY" /etc/fstab; then
  echo "Adding entry to /etc/fstab"
  echo "$FSTAB_ENTRY" | sudo tee -a /etc/fstab
else
  echo "Entry already exists in /etc/fstab"
fi

# Mount the S3 bucket
echo "Mounting the S3 bucket"
sudo mount -a
<!-- gh-comment-id:2577771803 --> @mvisser-nhb commented on GitHub (Jan 8, 2025): I rolled back to v1.94 and using iam_role=auto works again. Script I use to mount my s3 bucket, where I added checking out to v1.94, basically pinning it to that version ``` # Variables BUCKET_NAME="my-app-filestorage" MOUNT_POINT="/mnt/storage" NGINX_USER="nginx" NGINX_GROUP="nginx" # Ensure the mount point directory exists if [ ! -d "$MOUNT_POINT" ]; then echo "Creating mount point directory: $MOUNT_POINT" sudo mkdir -p "$MOUNT_POINT" fi # Install necessary dependencies and tools yum install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel -y git clone https://github.com/s3fs-fuse/s3fs-fuse.git cd s3fs-fuse git checkout v1.94 ./autogen.sh ./configure --prefix=/usr --with-openssl make make install ## Mount the S3 bucket with specific user and group ownership (nginx user) #s3fs $BUCKET_NAME $MOUNT_POINT -o iam_role=auto,uid=$(id -u $NGINX_USER),gid=$(id -g $NGINX_GROUP) # Add the entry to /etc/fstab for persistence FSTAB_ENTRY="s3fs#$BUCKET_NAME $MOUNT_POINT fuse _netdev,iam_role=auto,uid=$(id -u $NGINX_USER),gid=$(id -g $NGINX_GROUP),umask=0022,allow_other,nosuid,nodev 0 0" # Check if the entry already exists in /etc/fstab if ! grep -q "$FSTAB_ENTRY" /etc/fstab; then echo "Adding entry to /etc/fstab" echo "$FSTAB_ENTRY" | sudo tee -a /etc/fstab else echo "Entry already exists in /etc/fstab" fi # Mount the S3 bucket echo "Mounting the S3 bucket" sudo mount -a ```
kerem commented 2026-03-04 01:52:33 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Jan 18, 2025):

@ScottSorrentino @nikovolkov @mvisser-nhb Thanks for your kind reports.

I have confirmed that this is a bug in v1.95.
The cause is not the merge of github.com/s3fs-fuse/s3fs-fuse@efc23316e9 (this code has been merged since v1.95), but the addition of this line in #2535.
The current master branch also has a similar bug, and we are considering a fix for it.

<!-- gh-comment-id:2599743104 --> @ggtakec commented on GitHub (Jan 18, 2025): @ScottSorrentino @nikovolkov @mvisser-nhb Thanks for your kind reports. I have confirmed that this is a bug in v1.95. The cause is not the merge of https://github.com/s3fs-fuse/s3fs-fuse/commit/efc23316e9f5270e7821fe220dc5d2883f93c9ac (this code has been merged since v1.95), but the addition of [this line](https://github.com/s3fs-fuse/s3fs-fuse/blob/v1.95/src/curl_multi.cpp#L168) in #2535. The current master branch also has a similar bug, and we are considering a fix for it.
kerem commented 2026-03-04 01:52:33 +03:00
Author
Owner
Copy link

@ggtakec commented on GitHub (Jan 18, 2025):

This issue can be resolved by deleting this line, but the current master branch no longer has the code for this issue.
Instead, the iam_role authentication code was no longer working due to a different cause, so I am promoting a fix for #2635.
If you can use the master branch code, please use it after merging it.
(If you can only use the package, please use v1.94.)

<!-- gh-comment-id:2599764919 --> @ggtakec commented on GitHub (Jan 18, 2025): This issue can be resolved by deleting this [line](https://github.com/s3fs-fuse/s3fs-fuse/blob/v1.95/src/curl_multi.cpp#L168), but the current master branch no longer has the code for this issue. Instead, the `iam_role` authentication code was no longer working due to a different cause, so I am promoting a fix for #2635. If you can use the master branch code, please use it after merging it. (If you can only use the package, please use v1.94.)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.97
v1.96
v1.95
v1.94
v1.93
v1.92
v1.91
v1.90
v1.89
v1.88
v1.87
v1.86
v1.85
v1.84
v1.83
v1.82
v1.81
v1.80
v1.79
v1.78
Pre-v1.78
v1.77
v1.76
v1.75
v1.74
Labels
Clear labels   
bug

   
bug

   
dataloss

   
duplicate

   
enhancement

   
feature request

   
help wanted

   
invalid

   
need info

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
testing
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#1247
No description provided.