From 68562af8556d5ae28dceab44a20b3438cbe51f0c Mon Sep 17 00:00:00 2001 From: siddsriv Date: Wed, 12 Mar 2025 20:54:45 +0000 Subject: [PATCH 1/4] chore(supplemental-docs): md5 fallback for DeleteObjects update --- supplemental-docs/MD5_FALLBACK.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/supplemental-docs/MD5_FALLBACK.md b/supplemental-docs/MD5_FALLBACK.md index c620a1d4fadc..a4714ab233ef 100644 --- a/supplemental-docs/MD5_FALLBACK.md +++ b/supplemental-docs/MD5_FALLBACK.md @@ -6,8 +6,7 @@ In AWS SDK for JavaScript [v3.729.0](https://github.com/aws/aws-sdk-js-v3/releas we shipped a feature that [changed default object integrity in S3](https://github.com/aws/aws-sdk-js-v3/issues/6810). The SDKs now default to using more modern checksums (like CRC32) to ensure object integrity, whereas previously MD5 checksums were being used. -Some third-party S3-compatible services currently do not support these checksums. To our knowledge, -this affects only the S3 `DeleteObjects` operation. +Some third-party S3-compatible services currently do not support these checksums and require MD5 checksums. Furthermore, the `DeleteObjects` operation in S3 [requires a `Content-MD5` request header](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html) in which case too, you should use the MD5 fallback as noted below. If you wish to fallback to the old behavior of sending MD5 checksums, for operations like `DeleteObjectsCommand` this is how you can do it in AWS SDK for JavaScript v3: From 323d07422e94e5df8673c58199b383fe3a76e7a8 Mon Sep 17 00:00:00 2001 From: siddsriv Date: Wed, 12 Mar 2025 21:07:46 +0000 Subject: [PATCH 2/4] chore(supplemental-docs): line-wrap md --- supplemental-docs/MD5_FALLBACK.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/supplemental-docs/MD5_FALLBACK.md b/supplemental-docs/MD5_FALLBACK.md index a4714ab233ef..22ef77754c3c 100644 --- a/supplemental-docs/MD5_FALLBACK.md +++ b/supplemental-docs/MD5_FALLBACK.md @@ -2,14 +2,15 @@ ## Background -In AWS SDK for JavaScript [v3.729.0](https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.729.0), -we shipped a feature that [changed default object integrity in -S3](https://github.com/aws/aws-sdk-js-v3/issues/6810). The SDKs now default to using more modern -checksums (like CRC32) to ensure object integrity, whereas previously MD5 checksums were being used. -Some third-party S3-compatible services currently do not support these checksums and require MD5 checksums. Furthermore, the `DeleteObjects` operation in S3 [requires a `Content-MD5` request header](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html) in which case too, you should use the MD5 fallback as noted below. - +In AWS SDK for JavaScript v3.729.0, we +shipped a feature that changed default object integrity in S3. +The SDKs now default to using more modern checksums (like CRC32) to ensure object integrity, whereas +previously MD5 checksums were being used. Some third-party S3-compatible services currently do not +support these checksums and require MD5 checksums. Furthermore, the [DeleteObjects operation in S3 +requires a Content-MD5 request header](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html) +in which case too, you should use the MD5 fallback as noted below. If you wish to fallback to the old behavior of sending MD5 checksums, for operations like -`DeleteObjectsCommand` this is how you can do it in AWS SDK for JavaScript v3: +DeleteObjectsCommand this is how you can do it in AWS SDK for JavaScript v3: ## MD5 fallback From 57137b26b2817b6df8938c4846522ad682720ae8 Mon Sep 17 00:00:00 2001 From: siddsriv Date: Wed, 12 Mar 2025 21:09:07 +0000 Subject: [PATCH 3/4] chore(supplemental-docs): links --- supplemental-docs/MD5_FALLBACK.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/supplemental-docs/MD5_FALLBACK.md b/supplemental-docs/MD5_FALLBACK.md index 22ef77754c3c..a0249628f7a6 100644 --- a/supplemental-docs/MD5_FALLBACK.md +++ b/supplemental-docs/MD5_FALLBACK.md @@ -2,8 +2,8 @@ ## Background -In AWS SDK for JavaScript v3.729.0, we -shipped a feature that changed default object integrity in S3. +In AWS SDK for JavaScript [v3.729.0](https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.729.0), we +shipped a feature that [changed default object integrity in S3](https://github.com/aws/aws-sdk-js-v3/issues/6810). The SDKs now default to using more modern checksums (like CRC32) to ensure object integrity, whereas previously MD5 checksums were being used. Some third-party S3-compatible services currently do not support these checksums and require MD5 checksums. Furthermore, the [DeleteObjects operation in S3 From f4a241e9914a26aee0beb42ad9ad43b9dff872ca Mon Sep 17 00:00:00 2001 From: siddsriv Date: Wed, 12 Mar 2025 21:10:34 +0000 Subject: [PATCH 4/4] chore(supplemental-docs): minor nit --- supplemental-docs/MD5_FALLBACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/supplemental-docs/MD5_FALLBACK.md b/supplemental-docs/MD5_FALLBACK.md index a0249628f7a6..875dbc7aa15f 100644 --- a/supplemental-docs/MD5_FALLBACK.md +++ b/supplemental-docs/MD5_FALLBACK.md @@ -10,7 +10,7 @@ support these checksums and require MD5 checksums. Furthermore, the [DeleteObjec requires a Content-MD5 request header](https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteObjects.html) in which case too, you should use the MD5 fallback as noted below. If you wish to fallback to the old behavior of sending MD5 checksums, for operations like -DeleteObjectsCommand this is how you can do it in AWS SDK for JavaScript v3: +`DeleteObjectsCommand` this is how you can do it in AWS SDK for JavaScript v3: ## MD5 fallback