You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using boto3 client SDK within a notebook to interact with lakeFS instance in ECS. Looks like recent boto3 update (v1.36) made updates which are incompatible with LakeFS and now produces SignatureDoesNotMatch. Manually installing an earlier version resolves the issue
Expected behavior
Successful file upload
lakeFS version
No response
How lakeFS is installed
EC2
Affected clients
boto3
Relevant log output
File "/usr/local/lib/python3.10/site-packages/botocore/client.py", line 569, in _api_call
2025-01-24 14:12:37 onboarding |return self._make_api_call(operation_name, kwargs)
2025-01-24 14:12:37 onboarding | File "/usr/local/lib/python3.10/site-packages/botocore/client.py", line 1023, in _make_api_call
2025-01-24 14:12:37 onboarding | raise error_class(parsed_response, operation_name)
2025-01-24 14:12:37 onboarding | botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the PutObject operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Ouch, it seems like an unintentionally large change in boto3. This comment on that issue may be relevant; does it help as a workaround?
I must say the issue itself is still a bit unclear in terms of root cause and workarounds. Given that the workaround is not to update the SDK, and also that the AWS team will probably make more information available for this, I would prefer for us to wait for a few days and see how this evolves on the boto3 side.
Two ancient Hebrew sayings seem relevant. I hope I am proceeding according to the first one.
"צרת רבים חצי נחמה" - having the same problem as many others do is some consolation.
"צרת רבים נחמת טיפשים" - having the same problem as many others do is consolation for fools.
What happened?
Using boto3 client SDK within a notebook to interact with lakeFS instance in ECS. Looks like recent boto3 update (v1.36) made updates which are incompatible with LakeFS and now produces SignatureDoesNotMatch. Manually installing an earlier version resolves the issue
Expected behavior
Successful file upload
lakeFS version
No response
How lakeFS is installed
EC2
Affected clients
boto3
Relevant log output
Contact details
[email protected]
The text was updated successfully, but these errors were encountered: