[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[AI SDK](/c/ai-sdk/62)

# Bedrock client support for non-commercial AWS regions in Vercel AI SDK

12 views · 0 likes · 1 post


Gordon (@gordonshankman-7811) · 2026-03-05

See [Bedrock client doesn't support alternate URLs for non-standard AWS Regions. · Issue #11197 · vercel/ai · GitHub](https://github.com/vercel/ai/issues/11197).

## Problem
When the Vercel AI SDK moved away from the AWS libraries, support for all regions was not fully ported. Non-commercial regions do not use the `amazonaws.com` domain, and the endpoints do not resolve correctly.

## Current Behavior
The only configuration option is `baseUrl`, which doesn’t act as a base URL when configured; it acts as *the* URL for the Bedrock endpoint. This fails because there are at least two Bedrock endpoints required:

- `bedrock` 
- `bedrock-runtime` 

Currently, we can only set one of them via `baseUrl`. 

## Proposed Solution
The most future-proof solution is to use AWS’ native libraries for endpoint resolution, though this might conflict with existing design constraints. 

I plan on submitting a PR today with a patch for the current known regions. I am looking for acknowledgement on the bug report, as it has been open for over 2 months without a response.