AWS Bedrock

The Bedrock SDK reads AWS_* credentials from the environment; Aarmos only needs the HTTPS proxy env vars. No SDK patching.

1 · Environment

eval "$(aarmos env)"   # authenticated HTTPS_PROXY + HTTP_PROXY
export AWS_REGION=us-east-1
# AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY from your usual profile.

2 · Policy

# policy.aarmos.toml
[[allow]]
verb = "communicate"
host = "bedrock-runtime.*.amazonaws.com"
ceiling.per_minute = 60

3 · Run

aarmos run -- python agent.py    # daemon auto-starts on default port 7681

Notes

  • SigV4 signing is untouched — the proxy tunnels HTTPS by hostname without decrypting it, so the SDK's signature stays valid end to end.
  • Bedrock Guardrails, Agents, and Knowledge Bases are all governed under the same allow rule — they share the bedrock-runtime host.
  • For per-account isolation, add `principal.aws_account = "…"` as an ABAC attribute on the allow rule.

See all providers → recipes index.