xbcloud deprecate v2 support

Description

https://aws.amazon.com/blogs/aws/amazon-s3-update-sigv2-deprecation-period-extended-modified/

 

Amazon has deprecated sigv2 for s3 api. PXB still uses it for example, when your bucket and specified region on xbcloud don't match:

> HEAD / HTTP/1.1 Host: marce-pxb-test.s3.amazonaws.com Accept: */* Accept-Encoding: gzip Authorization: AWS4-HMAC-SHA256 Credential=AKIAZ72D65VBWVRG4OXQ/20201118/us-west-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-storage-class, Signature=abd645413005abbe0985420e5bc603a3f9f4447a3b97733415ed4f028f9efbe2 X-Amz-Content-SHA256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 X-Amz-Date: 20201118T113403Z x-amz-storage-class: GLACIER * Mark bundle as not supporting multiuse < HTTP/1.1 400 Bad Request < x-amz-bucket-region: us-west-2 < x-amz-request-id: F8389BE316C202DB < x-amz-id-2: UeDO18jsKVhF+tG/+YT3QIMXDsDBZvm4mPpn3GMzB99r51st01kXQaOr0+yFqTdbCS7has+KbcI= < Content-Type: application/xml < Date: Wed, 18 Nov 2020 11:34:04 GMT < Server: AmazonS3 < Connection: close

When this happens, we fall back to v2. Ideally, we should abort and either notify the customer about the issue or retry the request passing correct region.

Environment

None

Smart Checklist

Activity

Show:

Julia Vural February 19, 2025 at 11:58 AM

It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.

Won't Do

Details

Assignee

Reporter

Labels

Affects versions

Priority

Smart Checklist

Created November 18, 2020 at 11:58 AM
Updated February 19, 2025 at 11:58 AM
Resolved February 19, 2025 at 11:58 AM

Flag notifications