AWS SDK for Rust Receives Multiple Service Crate Updates in March 2026
Bedrock, SageMaker, ECS, and EC2 crates all shipped model updates in a busy March for the AWS SDK for Rust, with contributor @markuskobler also landing a sha1 dependency swap in aws-config.

A community contribution from @markuskobler landed alongside a fresh wave of service model bumps in the AWS SDK for Rust's March 4th release, swapping the sha1 calculation in `aws-config` from the `ring` crate to the standalone `sha1` crate. That dependency change, tracked under aws-sdk-rust#1317, arrived at a moment when the repository was already processing a broad set of upstream service updates, making this one of the more active stretches in the SDK's recent release calendar.
The March 3rd batch opened with `aws-sdk-bedrockagentcorecontrol` reaching 1.34.0 with support for AgentCore Policy GA, while `aws-sdk-cloudwatchlogs` hit 1.119.0 with a new `PutBearerTokenAuthentication` API for toggling bearer token authentication on individual log groups. The same wave pushed `aws-sdk-datazone` to 1.127.0 with a new `QueryGraph` operation, bumped `aws-sdk-partnercentralchannel` to 1.7.0 with changes to support plan options in the `CreateRelationship` and `UpdateRelationship` APIs, and moved `aws-sdk-sagemaker` to 1.185.0 with b300 and g7e instance types added for inference endpoints.
Compute crates also moved: `aws-sdk-ec2` climbed to 1.215.0 adding c8id, m8id, and hpc8a instance types, while `aws-sdk-ecs` reached 1.115.0 with Capacity Reservations support for ECS Managed Instances, introducing a new `capacityOptionType` value of `"RESERVED"` and a `capacityReservations` field in the `CreateCapacityProvider` and `UpdateCapacityProvider` APIs.
The SageMaker runtime crate, `aws-sdk-sagemakerruntime` at 1.98.0, gained `S3OutputPathExtension` and `Filename` parameters on the `InvokeEndpointAsync` API so developers can control the S3 output path and filename for async inference response payloads. A brand-new crate also shipped: `aws-sdk-signerdata` at 1.0.0, introducing the AWS Signer Data Plane SDK client with `GetRevocationStatus` API support and AWS PrivateLink connectivity for both private DNS and VPC endpoint URLs.

On the reliability front, `aws-sdk-arcregionswitch` updated to 1.19.0 with Post-Recovery Workflows, enabling disaster recovery automation that covers the entire recovery orchestration path from failover through post-recovery preparation. AWS Batch landed in 1.107.0 with the ability to specify a minimum instance runtime after jobs complete, while `aws-sdk-bedrock` at 1.134.0 gained four new model lifecycle date fields: `startOfLifeTime`, `endOfLifeTime`, `legacyTime`, and `publicExtendedAccessTime`.
Marketplace tooling received parallel updates, with `aws-sdk-marketplaceentitlement` at 1.101.0 adding License ARN as an optional filter in `GetEntitlements`, and `aws-sdk-marketplacemetering` at 1.99.0 picking up `LicenseArn` in `ResolveCustomer` responses and `BatchMeterUsage` records, plus a new `InvalidLicenseException` error type for invalid license parameters.
The SDK's modular design, which lets developers compile only the crates for the services they actually use, means most of these version bumps land as targeted Cargo.toml pin updates rather than broad recompilation events. The SDK currently requires a minimum of Rust 1.91.1, and any minimum version changes are called out explicitly in release notes. With the pace of service crate churn in March, teams pulling in multiple AWS clients should audit their lockfiles against the latest release manifest to confirm they are on current model versions before the next wave ships.
Know something we missed? Have a correction or additional information?
Submit a Tip
