Skip to content

added note that Gateways supports boto3 not newer than 1.35.99 #477

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Feb 28, 2025
Merged

added note that Gateways supports boto3 not newer than 1.35.99 #477

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
216aeeb
added note that Gateways supports boto3 not newer than 1.36.x
AlexeyALeonov Feb 28, 2025
3dcf4fe
fixed callout type
AlexeyALeonov Feb 28, 2025
646300f
added links to AWS docs
AlexeyALeonov Feb 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion app/(docs)/dcs/api/s3/s3-compatibility/page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -344,4 +344,19 @@ func main() {

fmt.Println(awsutil.Prettify(output))
}
```
```

## Compatibility with Python SDK (`boto3`) and `aws` CLI
Currently only `boto3` version up to 1.35.99 is working normally. Since AWS CLI uses `boto3` under the hood, it's affected too.

You can find the explanation of this breaking change in boto3 in this [github issue](https://github.com/boto/boto3/issues/4392).

{% callout type="warning" %}
Specifically, please note:

> Disclaimer: The AWS SDKs and CLI are designed for usage with official AWS services. We may introduce and enable new features by default, such as these new [default integrity protections](https://aws.amazon.com/blogs/aws/introducing-default-data-integrity-protections-for-new-objects-in-amazon-s3/) prior to them being supported or handled by third-party service implementations. You can disable the new behavior with the `WHEN_REQUIRED` value for the `request_checksum_calculation` and `response_checksum_validation` configuration options covered in [Data Integrity Protections for Amazon S3](https://docs.aws.amazon.com/sdkref/latest/guide/feature-dataintegrity.html).
{% /callout %}

It is preferable to downgrade rather than disabling the new behavior with `WHEN_REQUIRED`, and this may not even work with Storj anyway.

You may track [this issue](https://github.com/storj/gateway-st/issues/89) to be notified, when this new behavior would be supported by [Gateway-ST](docId:EGM8O-1xt2Az03eBWT8Rf) and [Gateway-MT](docId:yYCzPT8HHcbEZZMvfoCFa).