Cairn
NousResearch/hermes-agent

Bedrock profile config ignored, requires env var workaround

Cluster 43143 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

The bedrock.profile setting in config.yaml is not respected when initializing the boto3 client, forcing users to use the AWS_PROFILE environment variable instead. Multiple fix attempts address this configuration handling issue.

Open issues1

  • Issue#43143bedrock.profile in config.yaml is ignored, requires AWS_PROFILE environment variable

Open PRs2

  • PR#43139fix(bedrock): respect config.yaml bedrock.profile for boto3 client initialization
  • PR#43187fix(bedrock): respect bedrock.profile config for named AWS profiles (#43143)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #43266 fix(bedrock): respect bedrock.profile from config.yaml (#43143) · superseded by another PR → #43139, #43143
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/43143.json
cluster/43143.md