Version 4 (V4) of the Amazon SDK for .NET has been released!
For information about breaking changes and migrating your applications, see the migration topic.
Annual .NET target updates for the Amazon SDK for .NET
Starting with version 4.1, the Amazon SDK for .NET updates its .NET build targets once a year in a minor
version release. Each annual release adds builds for the .NET versions that Microsoft released during the
year. It removes builds for .NET versions that are no longer supported according to the Microsoft .NET
lifecycle
If your project targets a version of .NET that Microsoft supports, you can expect to update to the latest version of the SDK with no code changes.
Changes in version 4.1
Amazon released version 4.1 of the Amazon SDK for .NET on November 11, 2026, as the first release on the
annual schedule. For the announcement, see Announcing Amazon SDK for .NET
4.1
Updated build targets
Version 4.1 includes builds for .NET 11, .NET 10, and .NET 8, and for .NET Standard 2.0 and .NET Framework 4.7.2.
Version 4.1 removes the .NET Core 3.1 target. If your application targets .NET Core 3.1 or .NET 5, 6, or 7, it is out of support. Move it to a version of .NET that Microsoft supports. If you update the SDK without doing so, your project falls back to the .NET Standard 2.0 build of the SDK and you get a compile-time warning similar to the following:
warning : The target framework 'net6.0' is no longer supported by the AWS SDK for .NET. This project has fallen back to the .NET Standard 2.0 assemblies of the SDK, which do not include the features and optimizations available on supported targets.
The .NET Standard 2.0 build doesn't include target-specific features such as the Native AOT optimizations and bidirectional event stream APIs that are available in the .NET 8 and later builds.
The .NET 8 target remains in version 4.1 even though .NET 8 is out of support from Microsoft. For
information about how long it remains in the SDK, see Announcing Amazon SDK for .NET
4.1
Amazon Common Runtime (CRT) is no longer needed
Earlier versions of the SDK used .NET bindings to the native Amazon Common Runtime (CRT) for algorithms that
.NET didn't provide. These algorithms included SigV4a signing for Amazon S3 multi-region access points and
CRC64NVME checksums. If you used one of those features without the AWSSDK.Extensions.CrtIntegration
Starting with version 4.1, the SDK doesn't need CRT. A managed SigV4a implementation is part of the
AWSSDK.Core package, and checksums on all targets use the System.IO.HashingAWSSDK.Extensions.CrtIntegration, you can remove
the reference. Otherwise, the package is included in your deployment bundle and ignored.
Because .NET 8 and .NET 9 are out of support from Microsoft, projects that target them get a
compile-time warning from System.IO.Hashing similar to the following:
warning : System.IO.Hashing 11.0.0 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net10.0 or later.
The SDK's continuous integration tests exercise System.IO.Hashing for the ways in which
the SDK uses it. Update to a version of .NET that Microsoft supports. Alternatively, you
can suppress the warning by setting the SuppressTfmSupportBuildWarnings MSBuild property to
true in your project file.
Performance
Checksum calculation, such as the CRC32 checksum that the SDK calculates by default for Amazon S3 uploads,
now uses System.IO.Hashing instead of custom implementations in AWSSDK.Core.
This avoids allocations and is hardware accelerated on newer targets such as .NET 10 and .NET 11. Amazon
services are adding support for Concise Binary Object Representation (CBOR). The SDK uses CBOR
through the System.Formats.Cbor