[
https://issues.apache.org/jira/browse/HADOOP-19511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-19511:
------------------------------------
Summary: S3A: AWS4SignerType failing after S3 service changes (was: S3A:
AWS4SignerType failing)
> S3A: AWS4SignerType failing after S3 service changes
> ----------------------------------------------------
>
> Key: HADOOP-19511
> URL: https://issues.apache.org/jira/browse/HADOOP-19511
> Project: Hadoop Common
> Issue Type: Task
> Components: fs/s3
> Affects Versions: 3.4.0, 3.4.1
> Reporter: Steve Loughran
> Priority: Major
>
> With the latest change to the AWS S3 integrity, all existing releases of
> hadoop using the v2 SDK < 2.30.x appear to fail if the signer
> ```
> <property>
> <name>fs.s3a.bucket.signing-algorithm</name>
> <value>AWS4SignerType</value>
> </property>
> ```
> rejected at far end by
> ```
> Caused by: software.amazon.awssdk.services.s3.model.S3Exception: Missing
> required header for this request: x-amz-content-sha256 (Service: S3, Status
> Code: 400, Request ID: 7M0MNNE8NBAGZWFH, Extended Request ID:
> A/0oyoZ52GLklg+GuV70vqPNEAK350ZF1rTJaNtSajWSXLT5bUCC/Gu6VbN8Pu+AeaMboIIGyGHeFLXOKUwdVQ==)
> ```
> Presumably some change in 2.30.0 restored compatibility, but this means that
> all shipping 3.4.x releases do not work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
