Announcing Dome Managed Agents.

Try it now

Amazon Bedrock and Dome

Amazon Bedrock behind one Gateway, with every call governed. Connect Bedrock to Dome with your AWS credentials and a region. Dome signs each call and sends it through the Converse API. Pool Bedrock behind Anthropic and agents keep working when one provider fails.

Dome provides model brokeringand routing for Amazon Bedrock.

AWS credentials stay in Dome

Access keys sit in Dome's vault and sign each request with SigV4. Agents never hold an AWS credential.

Bedrock as the second provider

Pool Claude on Bedrock behind Anthropic under one name. When Anthropic fails, the call goes to Bedrock.

Accounts kept apart

Tag each connection with the AWS account it bills to. A rule keeps development agents off production.

Connect Bedrockin three steps.

Add the connection with your AWS keys, pool it, and point agents at the Gateway.
  1. Add it in the dashboard

    Choose Amazon Bedrock, then enter the AWS access key ID, secret access key, an optional session token, the region and the model id. Static AWS keys can only be set in the dashboard; the CLI has no flag for them.

  2. Pool it behind Anthropic

    Members are tried in priority order. Agents send the pool's name, and any OpenAI- or Anthropic-compatible client works.

    shell
    dome models pool create claude-sonnet-5-5 \  --failover-max all --gateway prod-gateway
    dome models pool member add claude-sonnet-5-5 sonnet-55-anthropic --priority 0dome models pool member add claude-sonnet-5-5 sonnet-55-bedrock --priority 1

Development agents stayoff the production account.

Tag each Bedrock connection with the AWS account it uses. Applied to a development agent with --agent, this refuses every connection tagged prod.
cedar
forbid (principal, action == Dome::Action::"llm:invoke", resource is Dome::LLMModel)when { resource has aws_account && resource.aws_account == "prod" };

Bringing it alltogether.

Connecting Amazon Bedrock to registered agents, tools, and identity in Dome completes a governed agent application.
Dome

Acting for

Control point

GatewayEvery call decided and audited
RulesGuardsQuotas

Common questionsabout Amazon Bedrock.

How does Dome authenticate to Amazon Bedrock?
With AWS access keys stored in Dome's vault, signed per request with SigV4.
Can I add AWS keys from the CLI?
No. Static AWS keys are set in the dashboard.
Which model id do I use?
The Bedrock model or inference profile id, such as us.anthropic.claude-sonnet-5-5. Dome sends it to the Converse API as given.
Do embeddings work on Bedrock connections?
No. Dome serves Bedrock chat through the Converse API; use another provider for embeddings.

More of whatDome works with.

Model

Claude Fable

Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
MCP server

GitHub

The GitHub MCP server behind the Tool Gateway, with rules that decide each call on its owner and repository.
Identity

Microsoft Entra ID

Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Runtime

LangGraph

LangGraph agents with their model calls on the Model Broker and their MCP tools on the Tool Gateway.
Client

Claude Code

Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service

TinyFish

TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.

Talk with ourFDE team.

Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.

LLM providers for AI agents: one governed path to every model

Connect a provider once. Its key stays in Dome, and every agent call to it is authorized, metered and audited.

Every agent you run, under one system of control.