fix(amazon-bedrock): extract region from inference profile ARNs#5527
Merged
badlogic merged 1 commit intoJun 9, 2026
Merged
Conversation
Application inference profile ARNs encode the region (arn:aws:bedrock:<region>:<account>:...) but the provider ignored it, falling through to AWS_REGION which may point to a different region. Extract the region from the ARN when present, taking priority over environment variables. Fixes earendil-works#4860
Collaborator
|
cheers |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Application inference profile ARNs encode the region
(
arn:aws:bedrock:<region>:<account>:...) but the provider ignored it,falling through to
AWS_REGIONwhich may point to a different region.Extract the region from the ARN when present, taking priority over
environment variables.
This is the solution proposed in #4860 (option 1: parse region from ARN).
Problem: In enterprise environments,
AWS_REGIONis commonly set toone region (e.g.
us-east-1) for general AWS CLI operations, whileBedrock inference profiles live in a different region (e.g.
us-west-2).The provider used
AWS_REGIONfor the Bedrock API call, causingValidationException: The provided model identifier is invalid.Fix: Add an ARN check as the first step in region resolution. If the
model ID matches
arn:aws:bedrock:<region>:..., use that region. Otherwisefall through to existing behavior (env vars, endpoint, defaults).
Fixes #4860