Amazon Bedrock provider requires API key in 1.14.29 (regression from 1.14.28)

[un0tec]

Description

Description: Amazon Bedrock provider is detected correctly (logs show providerID=amazon-bedrock found), and it appears in the provider selector, but the TUI prompts for an API key. Models from Bedrock do not appear in /models. Amazon Bedrock does not use API keys — it uses the AWS credential chain (SSO profiles, access keys, IAM roles, etc.).

Actual behavior: The provider selector asks for an API key. Without it, Bedrock models are not listed in /models.

Workaround: Downgrade to 1.14.28.

Plugins

None

OpenCode version

Affected version: 1.14.29 / 1.14.30

Working version: 1.14.28

Steps to reproduce

No response

Screenshot and/or share link

{ "enabled_providers": ["github-copilot", "amazon-bedrock"], "provider": { "amazon-bedrock": { "options": { "region": "eu-west-1", "profile": "xxx-bedrock" } } } }

Operating System

mac0S

Terminal

No response

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Bedrock connect dialog shows generic API key form instead of IAM credentials #14967: "Bedrock connect dialog shows generic API key form instead of IAM credentials" — describes the same symptom (Bedrock prompting for an API key instead of using the AWS credential chain). This was previously closed; the current issue may represent a regression/reintroduction in 1.14.29.
• Regression in 1.4.7/1.4.8: no providers load from project config (Bedrock); works in 1.4.6 #23110: "Regression in 1.4.7/1.4.8: no providers load from project config (Bedrock)" — also a Bedrock regression with a downgrade workaround, though the specific symptom differs.

If this is indeed a reintroduction of #14967, linking the two issues would help maintainers track the regression.

[un0tec]

This issue is still present in version 1.14.30

[un0tec]

Fixed in 1.14.33