SigV2 hasn't been supported on any AWS regions launched after 2013
SigV2 hasn't been supported on any AWS regions launched after 2013
The Europe (Frankfurt), US East (Ohio), Canada (Central), Europe (London), Asia Pacific (Seoul), Asia Pacific (Mumbai), Europe (Paris), China (Ningxia), Europe (Stockholm), Asia Pacific (Osaka Local), AWS GovCloud (US-East), and Asia Pacific (Hong Kong) Regions were launched after 2013, and support SigV4 but not SigV2. If you have code that accesses S3 buckets in that region, it is already making exclusive use of SigV4.


The HyperText Transfer Protocol (HTTP) 411 Length Required client error response code indicates that the server refuses to accept the request without a defined Content-Length header.
Content-Length header for uploads
Based on gitlab-org/gitlab-ee#4184 we know that only GCS (Google Cloud Storage) accepts chunked-encoding, all the other S3-compatible Object Storage requires Content-Length HTTP header.
enable_signature_v4_streaming ?x-amz-decoded-content-length header)Content-Lengthenable_signature_v4_streamingx-amz-decoded-content-length