Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Boto3 update may break SDK compatibility #8545

Open
rgparker1689 opened this issue Jan 24, 2025 · 2 comments
Open

[Bug]: Boto3 update may break SDK compatibility #8545

rgparker1689 opened this issue Jan 24, 2025 · 2 comments
Labels
bug Something isn't working contributor

Comments

@rgparker1689
Copy link

rgparker1689 commented Jan 24, 2025

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

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.

Contact details

[email protected]

@rgparker1689 rgparker1689 added bug Something isn't working contributor labels Jan 24, 2025
@rgparker1689
Copy link
Author

Perhaps relevant:
boto/boto3#4400

@arielshaqed
Copy link
Contributor

arielshaqed commented Jan 25, 2025

Oh wow, thanks for this bug report!

Perhaps relevant: boto/boto3#4400

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working contributor
Projects
None yet
Development

No branches or pull requests

2 participants