More aws-sdk-v3 issues

I'm now getting signature mismatch issues. I will try to dig in but not a JS developer nor do I have time.

Weirdly some of the files are uploaded successfully according to the logs before it blows up.

+- s3
| - validating config
| - Missing config: `fileIgnorePattern`, using default: `null`
| - Missing config: `prefix`, using default: ``
| - Missing config: `profile`, using default: ``
| - Missing config: `acl`, using default: `public-read`
| - Missing config: `cacheControl`, using default: `max-age=63072000, public, immutable`
| - Missing config: `expires`, using default: `Tue Jan 01 2030 00:00:00 GMT+0000 (Coordinated Universal Time)`
| - Missing config: `dotFolders`, using default: `false`
| - Missing config: `batchSize`, using default: `0`
| - Missing config: `defaultMimeType`, using default: `application/octet-stream`
| - Missing config: `distDir`, using default: `[Function]`
| - Missing config: `distFiles`, using default: `[Function]`
| - Missing config: `gzippedFiles`, using default: `[Function]`
| - Missing config: `brotliCompressedFiles`, using default: `[Function]`
| - Missing config: `manifestPath`, using default: `[Function]`
| - Missing config: `uploadClient`, using default: `[Function]`
| - Missing config: `s3Client`, using default: `[Function]`
| - config ok

+- upload
| |
| +- s3
| - Using AWS access key id and secret access key from config
| - preparing to upload to S3 bucket `REDACTED`
| - ✔ review.html
| - ✔ robots.txt
| - ✔ review-6076e4fc0df38aaf34a32042b9f139f7.map
| - ✔ oauth-6586b6d4629b3dff3aed4a0311d667a4.js
| ...
| - ✔ assets/chunk.app.d1f3c4eef12c516036e6.js
| - XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed.
| - XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed.
at throwDefaultError (/home/circleci/garaje/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)
at /home/circleci/garaje/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5
at de_CommandError (/home/circleci/garaje/node_modules/@aws-sdk/client-s3/dist-cjs/index.js:4756:14)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/circleci/garaje/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
at async /home/circleci/garaje/node_modules/@aws-sdk/middleware-signing/dist-cjs/index.js:225:18
at async /home/circleci/garaje/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
at async /home/circleci/garaje/node_modules/@aws-sdk/middleware-flexible-checksums/dist-cjs/index.js:173:18
at async /home/circleci/garaje/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:97:20
at async /home/circleci/garaje/node_modules/@aws-sdk/middleware-sdk-s3/dist-cjs/index.js:120:14
at async /home/circleci/garaje/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22

Commencez par reproduire l’échec de l’upload S3 et suivez le chemin de signature de AWS SDK v3 indiqué dans la stack trace, notamment @aws-sdk/client-s3 et @aws-sdk/middleware-signing. Comparez les fichiers qui sont uploadés avec succès à ceux qui produisent XAmzContentSHA256Mismatch ; c’est terminé lorsque le déploiement s’achève sans erreurs de non-correspondance de signature.

Rédigé par le modèle d'indexation à partir du texte de l'issue.