Skip to content

Backport: feat(bedrock): add support for service tier for model inference#14024

Merged
vercel-ai-sdk[bot] merged 1 commit intorelease-v6.0from
backport-pr-13242-to-release-v6.0
Apr 1, 2026
Merged

Backport: feat(bedrock): add support for service tier for model inference#14024
vercel-ai-sdk[bot] merged 1 commit intorelease-v6.0from
backport-pr-13242-to-release-v6.0

Conversation

@vercel-ai-sdk
Copy link
Copy Markdown
Contributor

@vercel-ai-sdk vercel-ai-sdk bot commented Apr 1, 2026

This is an automated backport of #13242 to the release-v6.0 branch. FYI @heiwen

## Background


https://docs.aws.amazon.com/bedrock/latest/userguide/service-tiers-inference.html

`@ai-sdk/amazon-bedrock` was missing request-side support for Bedrock
inference service tiers, despite Amazon Bedrock supporting them natively
for `Converse` / `ConverseStream` requests. This created a feature gap
relative to other AI SDK providers such as Groq, which already expose
request-level service tier controls.

Without this, Bedrock users could observe service tier information in
provider metadata, but could not select a tier through
`providerOptions`, even though the underlying Bedrock API supports it.

## Summary

This PR adds request-level Bedrock service tier support via
`providerOptions.bedrock.serviceTier`.

Changes included:
- Added `serviceTier` to `AmazonBedrockLanguageModelOptions`
- Validated supported values: `reserved`, `priority`, `default`, `flex`
- Serialized the option into Bedrock request bodies as top-level
`serviceTier: { type: ... }`
- Added generate and stream tests covering request serialization
- Added schema tests for accepted and rejected values
- Updated the Bedrock provider docs with a usage example
- Added a patch changeset for `@ai-sdk/amazon-bedrock`

## Manual Verification

Manually verified by exercising both `doGenerate` and `doStream` request
construction in the Bedrock provider tests and confirming the outgoing
request body includes:

```ts
serviceTier: {
  type: 'priority',
}
```

Also verified that:
- the value is sent as a top-level Bedrock request field, not under
`additionalModelRequestFields`
- invalid values are rejected by provider option validation
- existing request behavior remains unchanged when `serviceTier` is
omitted

## Checklist

- [x] Tests have been added / updated (for bug fixes / features)
- [x] Documentation has been added / updated (for bug fixes / features)
- [x] A _patch_ changeset for relevant packages has been added (for bug
fixes / features - run `pnpm changeset` in the project root)
- [x] I have reviewed this pull request (self-review)

## Related Issues

Fixes #13241

---------

Co-authored-by: Aayush Kapoor <83492835+aayush-kapoor@users.noreply.github.com>
Co-authored-by: Aayush Kapoor <aayushkapoor34@gmail.com>
@vercel-ai-sdk vercel-ai-sdk bot enabled auto-merge (squash) April 1, 2026 21:15
@tigent tigent bot added ai/provider related to a provider package. Must be assigned together with at least one `provider/*` label documentation Improvements or additions to documentation feature New feature or request provider/amazon-bedrock Issues related to the @ai-sdk/amazon-bedrock provider labels Apr 1, 2026
@vercel-ai-sdk
Copy link
Copy Markdown
Contributor Author

vercel-ai-sdk bot commented Apr 1, 2026

🚀 Published in:

Package Version
@ai-sdk/groq 3.0.32

@vercel-ai-sdk vercel-ai-sdk bot merged commit df099b9 into release-v6.0 Apr 1, 2026
26 checks passed
@vercel-ai-sdk vercel-ai-sdk bot deleted the backport-pr-13242-to-release-v6.0 branch April 1, 2026 21:22
@vercel-ai-sdk
Copy link
Copy Markdown
Contributor Author

vercel-ai-sdk bot commented Apr 1, 2026

🚀 Published in:

Package Version
@ai-sdk/amazon-bedrock 4.0.87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai/provider related to a provider package. Must be assigned together with at least one `provider/*` label documentation Improvements or additions to documentation feature New feature or request provider/amazon-bedrock Issues related to the @ai-sdk/amazon-bedrock provider

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants