# NousResearch/hermes-agent · Bedrock service tier and performance config support

## Open now

- 1 issue, 0 PRs open on GitHub.
- #31322: \[Feature\]: Support \`service_tier\` for Amazon Bedrock

These items relate to adding service_tier and performanceConfig options for Amazon Bedrock, along with a fix for using Claude's native output limits.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Open related issues

- #31322: \[Feature\]: Support \`service_tier\` for Amazon Bedrock

## Prior & competing PRs

- **#34476: feat(bedrock): support service_tier and performanceConfig for cost/latency control**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `9e6c4100c`, `#31322`
- **#37309: fix(bedrock): use Claude native output limits**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `0cb8c51fa582e382a5365cbc4bd9a3f7eb2fe280`

## Fix status

- No merged fix on record.
- Subsystem: `agent`