Description
AWS has deprecated the AWSSDK.Extensions.Bedrock.MEAI package. The NuGet listing is now marked deprecated with the message:
This package has been deprecated as it is legacy and is no longer maintained.
NuGet lists AWS.Bedrock.MEAI as the replacement. The extension has been renamed and moved out of aws/aws-sdk-net into the new AI Integrations on AWS for .NET repository, aws/aws-dotnet-ai, where it now releases independently.
|
Old |
New |
| Package |
AWSSDK.Extensions.Bedrock.MEAI |
AWS.Bedrock.MEAI |
| Latest version |
4.0.101.8 (deprecated) |
1.0.0 (stable, 2026-08-11) |
| Repository |
aws/aws-sdk-net |
aws/aws-dotnet-ai |
This repo currently references the deprecated package in three places:
dotnet/Directory.Packages.props (line 145) — <PackageVersion Include="AWSSDK.Extensions.Bedrock.MEAI" Version="4.0.101.8" />
dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock.csproj — <PackageReference>
dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock/README.md — two prose mentions
Because the package is deprecated, Dependabot will no longer surface version bumps for it (the last one was #7829), so the Bedrock sample is now pinned to an unmaintained adapter and will silently miss upstream fixes.
Migration impact
This is a drop-in swap — no source changes are required. Per the new package's README, the AmazonBedrockRuntimeExtensions methods (AsIChatClient, AsIEmbeddingGenerator, etc.) remain in the Amazon.BedrockRuntime namespace. Only the package identity and version change. The package's own types (e.g. BedrockStructuredOutputMode) now live in the AWS.Bedrock.MEAI namespace, but the sample does not reference any of those.
Target frameworks are unchanged in the relevant direction: the new package supports net472, netstandard2.0, and net8.0, and the sample targets net10.0.
I verified locally that swapping the package reference builds the sample cleanly (Build succeeded. 0 Warning(s), 0 Error(s)) with Program.cs untouched.
Steps to reproduce
- Open
dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock.
- Restore packages.
- Observe that
AWSSDK.Extensions.Bedrock.MEAI 4.0.101.8 resolves to a package deprecated on nuget.org.
Expected behavior
The repo references the maintained AWS.Bedrock.MEAI package so the Bedrock sample keeps receiving upstream updates and Dependabot coverage.
Proposal
Rename the package reference in Directory.Packages.props to AWS.Bedrock.MEAI version 1.0.0, update the sample's PackageReference, and update the two README mentions. I'm happy to open the PR — I have the change made and building locally.
Description
AWS has deprecated the
AWSSDK.Extensions.Bedrock.MEAIpackage. The NuGet listing is now marked deprecated with the message:NuGet lists
AWS.Bedrock.MEAIas the replacement. The extension has been renamed and moved out of aws/aws-sdk-net into the new AI Integrations on AWS for .NET repository, aws/aws-dotnet-ai, where it now releases independently.AWSSDK.Extensions.Bedrock.MEAIAWS.Bedrock.MEAIThis repo currently references the deprecated package in three places:
dotnet/Directory.Packages.props(line 145) —<PackageVersion Include="AWSSDK.Extensions.Bedrock.MEAI" Version="4.0.101.8" />dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock.csproj—<PackageReference>dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock/README.md— two prose mentionsBecause the package is deprecated, Dependabot will no longer surface version bumps for it (the last one was #7829), so the Bedrock sample is now pinned to an unmaintained adapter and will silently miss upstream fixes.
Migration impact
This is a drop-in swap — no source changes are required. Per the new package's README, the
AmazonBedrockRuntimeExtensionsmethods (AsIChatClient,AsIEmbeddingGenerator, etc.) remain in theAmazon.BedrockRuntimenamespace. Only the package identity and version change. The package's own types (e.g.BedrockStructuredOutputMode) now live in theAWS.Bedrock.MEAInamespace, but the sample does not reference any of those.Target frameworks are unchanged in the relevant direction: the new package supports
net472,netstandard2.0, andnet8.0, and the sample targetsnet10.0.I verified locally that swapping the package reference builds the sample cleanly (
Build succeeded. 0 Warning(s), 0 Error(s)) withProgram.csuntouched.Steps to reproduce
dotnet/samples/02-agents/AgentWithMemory/AgentWithMemory_Step03_MemoryUsingValkey_Bedrock.AWSSDK.Extensions.Bedrock.MEAI4.0.101.8 resolves to a package deprecated on nuget.org.Expected behavior
The repo references the maintained
AWS.Bedrock.MEAIpackage so the Bedrock sample keeps receiving upstream updates and Dependabot coverage.Proposal
Rename the package reference in
Directory.Packages.propstoAWS.Bedrock.MEAIversion1.0.0, update the sample'sPackageReference, and update the two README mentions. I'm happy to open the PR — I have the change made and building locally.