Hermes Agent Bedrock: Run Hermes on AWS Bedrock Models

Hermes Agent Bedrock support lets you run Hermes on models hosted in your own AWS account — Claude, Nova, DeepSeek, Llama and more — through Amazon Bedrock. Hermes uses Bedrock’s Converse API, so one setup works across model families, and it uses your normal AWS credentials. In the video below I cover a new model landing on Bedrock. Here’s how to connect Hermes to Bedrock step by step.

Why use Hermes Agent with Bedrock

• Your AWS account — billing, limits and data handling stay inside AWS.
• Company compliance — many businesses already approve Bedrock.
• One provider, many models — Claude, Nova, DeepSeek, Llama and others.
• Guardrails — apply Bedrock Guardrails to agent output.
• Cross-region inference for availability.

Hermes Agent Bedrock setup

The easy way: run hermes model and choose “AWS Bedrock”.

From the command line:

hermes chat --provider bedrock --model us.anthropic.claude-sonnet-4-6

With a specific AWS profile and region:

AWS_PROFILE=myprofile AWS_REGION=us-east-1 hermes chat --provider bedrock --model us.anthropic.claude-sonnet-4-6

Swap in any Bedrock model ID you have access to.

Hermes Agent Bedrock config.yaml

To make Bedrock your default, add this to your Hermes config:

model:
  provider: "bedrock"
  default: "us.anthropic.claude-sonnet-4-6"
bedrock:
  region: "us-east-1"
  # profile: "myprofile"
  # guardrail:
  #   guardrail_identifier: "your-guardrail-id"
  #   guardrail_version: "DRAFT"

Set BEDROCK_BASE_URL only if you need a non-default regional endpoint.

AWS credentials for Hermes

Hermes uses the standard AWS credential chain, so if the AWS CLI already works on your machine, Hermes will too. That covers access keys, a named profile in ~/.aws/credentials, IAM roles, instance metadata on EC2, and SSO. Your IAM user or role needs permission to invoke the Bedrock models you want, and model access must be enabled in the Bedrock console for your region.

Choosing a Bedrock model for Hermes

Agents need plenty of context — Hermes needs at least 64K — so pick models with large context windows.

Hermes Agent Bedrock troubleshooting

• Access denied — enable model access in the Bedrock console and check IAM permissions.
• Model not found — check the model ID and that it’s available in your region.
• Wrong account — set AWS_PROFILE explicitly.
• Slow or throttled — try cross-region inference or request a quota increase.

The bottom line on Hermes Agent Bedrock

Hermes Agent Bedrock setup takes a few minutes: choose AWS Bedrock in hermes model, use your normal AWS credentials, and pick a model. It’s the best route if your business already runs on AWS.

FAQ: hermes agent bedrock

Does Hermes Agent support AWS Bedrock?

Yes — with the built-in bedrock provider, using Bedrock’s Converse API.

How do I connect Hermes to Bedrock?

Run hermes model and choose AWS Bedrock, or use hermes chat –provider bedrock –model followed by a model ID.

Do I need a special Hermes key for Bedrock?

No — Hermes uses your standard AWS credentials.

Which models can Hermes use on Bedrock?

Claude, Nova, DeepSeek, Llama and other models you have access to in your region.

Can I use Bedrock Guardrails with Hermes?

Yes — add a guardrail identifier and version under bedrock in config.yaml.

About Julian Goldie

I’m Julian Goldie — founder of Goldie Agency, best-selling author, and an AI educator with 428K+ YouTube subscribers. I’ve spent 10+ years in SEO and online business and I test every AI agent on my own work before I recommend it. Join the AI Profit Boardroom for the daily builds, or book a free strategy session to talk through yours.

Related reading

• Best Hermes Agent Model
• Hermes Agent Backend
• Hermes Agent by Nous Research

Last updated October 2026. This page is a living guide to hermes agent bedrock — the facts here move fast and it is updated as they do.