S3 pipelines on SDC v5.6.0 failing with AmazonS3Exception:SignatureDoesNotMatch after upgrading to v5.6.0 from v5.5.0

  • 13 July 2023
  • 1 reply

we upgraded data collector to v5.6.0 from v5.5.0 recently… but since then getting our s3 pipelines are failing with below ERROR.. we are using `Instance Profile` as authentication method..

Also data collector with v5.5.0 which are deployed same (AWS acc)environment are working fines with s3 pipelines & instance_profile authentication method. anyone else faced similar kind of problem?

RETRY: S3_21 - Unable to write object to Amazon S3, reason : The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: 3VFHG02TG4GR3KTR; S3 Extended Request ID: PePeTM0p51ZFcECJ/Mw6PU9nK4Km6AWNEaWhcykqj2ovDW/IbGcMtcaK+xcRxlMoPuRlCyxh2vo=; Proxy: null), S3 Extended Request ID: PePeTM0p51ZFcECJ/Mw6PU9nK4Km6AWNEaWhcykqj2ovDW/IbGcMtcaK+xcRxlMoPuRlCyxh2vo=

1 reply


It appears that this error is the result of the updates made by Amazon to their latest AWS SDK, which is the one being used in your current SDC version 5.6.0. This is a change from the SDK used in SDC 5.5.0, so there will be an upgrade impact for all pipelines using Amazon S3 staging. Please refer to the Upgrade Impact in our Release Notes for more details and an example of how to solve this issue.