Skip to content

Commit

Permalink
docs(client-s3): update changelog for default data integrity protecti…
Browse files Browse the repository at this point in the history
…ons (#6807)
  • Loading branch information
trivikr authored Jan 15, 2025
1 parent 376b453 commit 4ab6bd1
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline
* **client-bedrock-agent-runtime:** Now supports streaming for inline agents. ([b6204f8](https://github.com/aws/aws-sdk-js-v3/commit/b6204f8b03f81157efd5b6d7ee746c578dec4160))
* **client-cognito-identity:** corrects the dual-stack endpoint configuration ([b5c504b](https://github.com/aws/aws-sdk-js-v3/commit/b5c504b00ff9c8de1207813a2604e86dfc438135))
* **client-partnercentral-selling:** Add Tagging support for ResourceSnapshotJob resources ([482229b](https://github.com/aws/aws-sdk-js-v3/commit/482229be2e40d1bfe5f37ca96b26a4fdf12bd426))
* **client-s3:** This change enhances integrity protections for new SDK requests to S3. S3 SDKs now support the CRC64NVME checksum algorithm, full object checksums for multipart S3 objects, and new default integrity protections for S3 requests. ([a550721](https://github.com/aws/aws-sdk-js-v3/commit/a550721e05a76f741c9a702aefd27c32da06aa27))
* **client-s3:** S3 client behavior is updated to always calculate CRC32 checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). Checksum behavior can be configured using `when_supported` and `when_required` options - in code using `requestChecksumCalculation`, in shared config using `request_checksum_calculation`, or as env variable using `AWS_REQUEST_CHECKSUM_CALCULATION`. The S3 client also attempts to validate response checksums for all S3 API operations that support checksums. Checksum validation behavior can be configured using `when_supported` and `when_required` options - in code using `responseChecksumValidation`, in shared config using `response_checksum_validation`, or as env variable using `AWS_RESPONSE_CHECKSUM_VALIDATION`. We also added support for the CRC64NVME checksum algorithm in S3 client through optional AWS CRT dependency from `aws-crt`. ([a550721](https://github.com/aws/aws-sdk-js-v3/commit/a550721e05a76f741c9a702aefd27c32da06aa27))
* **client-security-ir:** Increase minimum length of Threat Actor IP 'userAgent' to 1. ([635576b](https://github.com/aws/aws-sdk-js-v3/commit/635576b77e997395c3f126f30b71cb1085b1bb15))
* **client-sesv2:** This release introduces a new recommendation in Virtual Deliverability Manager Advisor, which detects elevated complaint rates for customer sending identities. ([df28319](https://github.com/aws/aws-sdk-js-v3/commit/df283196cf1428fb7ca9065be099c842601b8b62))
* **client-workspaces-thin-client:** Mark type in MaintenanceWindow as required. ([660165d](https://github.com/aws/aws-sdk-js-v3/commit/660165d6b7fa10845e269924dad12166fcbeff71))
Expand Down

0 comments on commit 4ab6bd1

Please sign in to comment.