-
Notifications
You must be signed in to change notification settings - Fork 863
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Announcement: S3 default integrity change #3610
Labels
Comments
This was referenced Jan 20, 2025
1 task
nhulston
added a commit
to DataDog/dd-trace-dotnet
that referenced
this issue
Feb 3, 2025
nhulston
added a commit
to DataDog/dd-trace-dotnet
that referenced
this issue
Feb 3, 2025
1 task
IMHO, this is a breaking change that should not be included in a minor version update. Most deployments have 50+ packages to update and won't go read every announcement on github. |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In AWS SDK for .NET package AWSSSDK.S3 version 3.7.412.0, we released changes to the S3 client that adopts new default integrity protections. For more information on default integrity behavior, please refer to the official SDK documentation. In SDK releases from this version on, clients default to enabling an additional checksum on all Put calls and enabling validation on Get calls.
You can instead disable default integrity protections for S3. We do not recommend this because checksums are important to S3 integrity posture. Integrity protections can be disabled by setting the config flag
RequestChecksumCalculation
toWHEN_REQUIRED
, or by using the related AWS shared config file settings or environment variables.Disclaimer: the AWS SDKs and CLI are designed for usage with official AWS services. We may introduce and enable new features by default, such as these new default integrity protections, prior to them being supported or otherwise handled by third-party service implementations. You can disable the new behavior with the
WHEN_REQUIRED
value for therequest_checksum_calculation
andresponse_checksum_validation
configuration options covered in Data Integrity Protections for Amazon S3.The text was updated successfully, but these errors were encountered: