Skip to content

V2: bring Bedrock Converse native auth and config to parity #34997

Closed

Description

@rekram1-node

Context

Native Bedrock Converse exists, but it does not yet match AI SDK plugin behavior for common AWS credential and region setups.

Scope

  • Add default AWS credential chain/profile/container credential behavior where appropriate.
  • Support Bedrock bearer token environment behavior.
  • Review region, endpoint override, cross-region inference profiles, guardrails, performance config, and model-specific request fields.
  • Keep Converse separate from Mantle.

Acceptance Criteria

  • Common AI SDK Bedrock auth/config paths have native equivalents.
  • Runner/catalog mapping can safely choose native Bedrock Converse for supported models.
  • Recorded or fixture tests cover credential-chain and request-shape behavior.

Activity

  1. self-assigned this
    on Jul 2, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Jul 2, 2026
  3. neriousy commented on Oct 21, 2026

    @neriousy
    Member

    Mostly done: native Bedrock now uses the AWS default credential chain with profiles (#47436), bearer token auth, credential discovery (#47548), an AWS profile picker (#53626) and inference-profile IDs (#48078, #54486). Still missing: guardrailConfig and performanceConfig passthrough in bedrock-converse. Closing this tracker. If those are needed, a focused issue for them is easier to pick up.

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

Metadata

Metadata

Assignees

Labels

2.0coreAnything pertaining to core functionality of the application (opencode server stuff)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions