BestPaid guides · AWS · .NET

AWS SDK for .NET V3 reached end of support on June 1, 2026: how to move to V4

AWS no longer releases V3 of the AWS SDK for .NET (the AWSSDK.* packages) or AWS Tools for PowerShell V4, not even security fixes. Here is what that means and how to move to V4.

Sources: AWS's SDK for .NET V3 end-of-support (June 1, 2026), maintenance mode (March 4, 2026) and first (August 19, 2025) announcements; the Tools for PowerShell V4 first end-of-support announcement (August 19, 2025), V4 end-of-support post and V5 GA post; the maintenance policy and version support matrix; the V4 guide's migration, platforms and annual target updates pages (the platforms page updated and the target updates page added on November 12, 2026, per its document history) and AWSConfigs reference; AWS's V4.0 GA, preview 1, preview 4, annual target schedule and 4.1 posts; the V4 tracker on GitHub; the PowerShell V5 migration guide; Lambda's runtime deprecation page; Microsoft Learn's dotnet package list, dotnet nuget why and Get-Module pages; and NuGet package data. Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

The dates AWS gives

DateWhat happened
April 28, 2025SDK V4.0 generally available
June 23, 2025AWS Tools for PowerShell V5, built on SDK V4, generally available
August 19, 2025End of support announced for SDK V3 and Tools for PowerShell V4
March 1, 2026Both in maintenance mode: critical bug and security fixes only
June 1, 2026End of support for both
November 11, 2026SDK 4.1: builds for .NET 11, 10 and 8, .NET Standard 2.0 and .NET Framework 4.7.2; .NET Core 3.1 dropped
November 2027 (planned)SDK 4.2 drops .NET 8 (may slip to December)

What end of support means

1. Find every AWSSDK.* package

AWS says V3 and V4 packages can't be mixed in one app, so all references move together. List them per solution:

# .NET 10 SDK or later
dotnet package list --include-transitive --format json > packages.json

# .NET 9 SDK or earlier
dotnet list package --include-transitive

# What pulls in AWSSDK.Core? (.NET 8.0.4xx SDK or later)
dotnet nuget why AWSSDK.Core

Also search repositories for AWSSDK. to catch packages.config files and checked-in DLLs. Libraries on the SDK have their own versions; these are from AWS's V4 tracker, with the first stable V4-based version on NuGet (check third-party ones there too):

PackageFirst on V4
AWS.Logger.Core and AWS.Logger.* providers4.0.0
Amazon.Extensions.Configuration.SystemsManager7.0.0
Amazon.AspNetCore.DataProtection.SSM4.0.0
AWSSDK.SecretsManager.Caching2.0.0
Amazon.Extensions.S3.Encryption3.0.0
Amazon.Lambda.DynamoDBEvents.SDK.Convertor2.0.0
Amazon.Lambda.KinesisEvents3.0.0
OpenTelemetry.Instrumentation.AWS1.12.0

2. The breaking changes AWS documents

Build breaks. Value-type properties on requests and responses become nullable (bool?, int?, long?, double?, float?, DateTime?); where code doesn't recompile, AWS suggests .Value or GetValueOrDefault(). Removed APIs:

Removed in V4Use instead
STSAssumeRoleAWSCredentialsAssumeRoleAWSCredentials
StoredProfileAWSCredentials, StoredProfileCredentials, ProfileManagerNetSDKCredentialsFile or SharedCredentialsFile
ECSTaskCredentialsGenericContainerCredentials
AmazonS3Util.DoesS3BucketExist(Async)DoesS3BucketExistV2(Async)
S3 encryption client, CloudFront signers, EC2 GetDecryptedPasswordAmazon.Extensions.S3.Encryption, AWSSDK.Extensions.CloudFront.Signers, AWSSDK.Extensions.EC2.DecryptPassword
DynamoDB Streams in AWSSDK.DynamoDBv2AWSSDK.DynamoDBStreams
Lambda InvokeAsync(InvokeAsyncRequest), InvokeAsyncAsyncInvoke or InvokeAsync(InvokeRequest)
DefaultClientConfig.HttpClientFactoryAWSConfigs.HttpClientFactory
UTC twins such as StartTimeUtcThe original name (StartTime), now UTC

Behavior changes.

// Null when no messages came back (V3: empty list)
foreach (var message in response.Messages ?? new List<Message>())
    await HandleAsync(message);

// Stop-gap V3 behavior, costs V4's performance gains; set once at startup
// (AWS: not thread safe)
Amazon.AWSConfigs.InitializeCollections = true;

3. Target frameworks

4. AWS Tools for PowerShell V4 to V5

Get-Module -ListAvailable -Name AWS.Tools.*, AWSPowerShell* | Select-Object Name, Version
Update-AWSToolsModule    # AWS.Tools modules; V5 is the default

In V5 the legacy AWSPowerShell module needs PowerShell 5.1 and .NET Framework 4.7.2 or later. Script changes:

5. Upgrade order

  1. Inventory apps, packages, libraries and PowerShell hosts; start with the best-tested app.
  2. Optional: in a V3 test run, set AWSConfigs.InitializeCollections (default true in late V3 releases) to false to find null-collection bugs.
  3. Retarget .NET Framework apps below 4.7.2.
  4. Move AWSSDK.Core and every service package to the current 4.1.x, and the libraries above to their V4 versions, at once.
  5. Fix the build, then null collections, S3 Regions, credentials, logging and DynamoDB settings.
  6. Test in a development environment before production, as AWS advises.
  7. Move .NET Core 3.1 to .NET 9 apps to .NET 10 separately (our .NET 8 to .NET 10 checklist); on Lambda, that means leaving the dotnet8 runtime, deprecated November 10, 2026, for dotnet10 (our Lambda dotnet8 guide).

6. Tests that catch V4 problems

Still on AWSSDK V3 packages? We upgrade .NET apps at a fixed price, including the move to the AWS SDK for .NET V4 and to .NET 10. It starts with a $490 audit: every project, package and breaking change, with a fixed quote.
See the .NET upgrade offer