Customer gets 403 error from s3 "SignatureDoesNotMatch..." after upgrading to concourse 7.14.1

Products

• Operations Manager

Issue/Introduction

The customer recently upgraded to Concourse 7.14.1 or newer, and when running pipelines, they are seeing errors similar to the following:

error running command: upload multipart failed, upload id: 11######73, cause: operation error S3: UploadPart, https response error StatusCode: 403, RequestID: 17######38, HostID: #############################, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your HCP Secret Access Key and signing method.

Environment

Concourse 7.14.1 or newer.

Cause

The customer may be using an older S3 backend. v7.14.1 of Concourse ships with S3 v2.4.0, which enforces a checksum verification on file upload. Older S3 backends may not support checksums with file transfers.

Resolution

The customer can disable s3 checksums by setting the skip_s3_checksums option in their s3 configuration.