AWS Bedrock
AWS Bedrock
Start with meaning, then move to detail.
This lesson explains AWS Bedrock as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Prerequisites, Quick Start, Configuration, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand AWS Bedrock without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
Use Hermes Agent with Amazon Bedrock — native Converse API, IAM authentication, Guardrails, and cross-region inference
What does the source say, and in what order?
- 01Prerequisites
Start here to understand the core idea or structure.
- 02Quick Start
Read this after the foundation, then connect it to the previous step.
- 03Configuration
Read this after the foundation, then connect it to the previous step.
- 04Region
Read this after the foundation, then connect it to the previous step.
- 05Guardrails
Read this after the foundation, then connect it to the previous step.
- 06Model Discovery
Read this after the foundation, then connect it to the previous step.
- 07Prompt caching (cachePoint)
Read this after the foundation, then connect it to the previous step.
- 08Context-window probing
Read this after the foundation, then connect it to the previous step.
- 09Available Models
Read this after the foundation, then connect it to the previous step.
- 10Switching Models Mid-Session
Finish here to verify the result and special cases.
Copy only after you understand the effect.
# Install with Bedrock support
cd ~/.hermes/hermes-agent && uv pip install -e ".[bedrock]"
# Select Bedrock as your provider
hermes model
# → Choose "More providers..." → "AWS Bedrock"
# → Select your region and model
# Start chatting
hermes chatmodel:
default: us.anthropic.claude-sonnet-4-6
provider: bedrock
base_url: https://bedrock-runtime.us-east-2.amazonaws.com
bedrock:
region: us-east-2bedrock:
region: us-east-2
guardrail:
guardrail_identifier: "abc123def456" # From the Bedrock console
guardrail_version: "1" # Version number or "DRAFT"
stream_processing_mode: "async" # "sync" or "async"
trace: "disabled" # "enabled", "disabled", or "enabled_full"Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.