[BUG] Custom ARN Regex for AWS Bedrock is too strict

[wisestmumbler]

Problem (one or two sentences)

Expected to be able to add a custom ARN for aws-us-gov but roo code does not believe it is valid

Context (who is affected and when)

Happens when a user attempts to add a custom ARN for aws-us-gov

Reproduction steps

Roo Code VSCode Plugin v3.33.3 (windows)
Using AWS Provider with the settings in screenshot attached

Example Custom ARN:
arn:aws-us-gov:bedrock:us-gov-west-1:123456789012:inference-profile/us-gov.anthropic.claude-sonnet-4-5-20250929-v1:0

Expected result

Should accept the arn

Actual result

"Invalid ARN format. Please check the format requirements." and fails to run

Variations tried (optional)

Changing arn to arn:aws:bedrock... fails to actually resolve because the "-us-gov" is required by bedrock

ref: https://github.com/RooCodeInc/Roo-Code/blob/main/webview-ui/src/utils/validate.ts#L228C40-L228C49
(maybe more places too?)

App Version

v3.33.3

API Provider (optional)

AWS Bedrock

Model Used (optional)

us-gov.anthropic.claude-sonnet-4-5-20250929-v1:0

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for the AWS GovCloud ARN validation issue and will open a PR to share progress.

[roomote]

Opened PR #9482 with my attempt at addressing this issue. The fix adds support for AWS GovCloud (aws-us-gov) and China (aws-cn) region ARNs in the Bedrock validation logic. Feedback welcome!

[wisestmumbler]

@roomote does the solution for #10108 solve this issue too?

[roomote]

Yes, the solution for #10108 (PR #10110) does solve this issue as well.

PR #10110 was merged on December 16, 2025 and removes the strict ARN regex validation entirely from the validateBedrockArn() function. Instead of trying to match specific ARN formats, it now always returns isValid: true for any ARN input.

This means your arn:aws-us-gov:bedrock:us-gov-west-1:123456789012:inference-profile/us-gov.anthropic.claude-sonnet-4-5-20250929-v1:0 ARN (and any other valid ARN format) should now be accepted without validation errors.

This issue can likely be closed as resolved by #10110.

[bgiaccio]

@wisestmumbler I've updated to 3.36.10
The arn saves in the settings but when I type anything at the prompt I get "Failed to create task: INVALID_ARN_FORMAT. Arn should follow the Amazon Bedrock ARN pattern."

My arn is arn:aws-us-gov:bedrock:us-gov-west-1:123456789012:inference-profile/us-gov.anthropic.claude-sonnet-4-5-20250929-v1:0

[wisestmumbler]

@roomote I get the same error @bgiaccio is seeing above with my real arn (same format as his)

it allows me to input the custom arn but then results in a Failed to create api configuration error so I think I am still blocked despite the changes in #10110

then when I run a task with the arn saved in there I get the error that he posted:

Failed to create task: INVALID_ARN_FORMAT:Invalid ARN format. ARN should follow the Amazon Bedrock ARN pattern.

fyi @mrubens