Kapālins for Amazon Bedrock
Claude, Llama, Mistral, Nova and Titan, served from your own AWS account. Kapālins signs every call to Bedrock with SigV4, checks the prompt and the reply on the way through, and reads CloudTrail for the Bedrock calls that never came through the gateway.
Your AWS boundary, one policy on top
Inference stays in the AWS region your credential names. Kapālins adds the same redaction, injection defence and per-team policy you run on every other provider.
The calls that skipped the gateway
The AWS CloudTrail connector reads bedrock.amazonaws.com events, so a model called straight from a notebook or a Lambda still shows up, named by its IAM principal.
Every model family, judged separately
Claude on Bedrock, Llama on Bedrock and Nova are probed and approved one by one, through your own AWS credentials.
Inline on every call. CloudTrail for the rest.
Every governed call, checked both ways
Your application calls the gateway in the OpenAI or Anthropic format. Kapālins inspects the prompt, signs the request with SigV4, sends it to Bedrock InvokeModel in your region, and inspects the reply before it lands.
- Request shapes for Claude, Llama, Mistral, Nova, Titan, Cohere and Jamba
- Cross-region inference profiles: us., eu. and apac.
- Your models listed live from your account when you connect
Every Bedrock call, even the direct ones
CloudTrail records Bedrock calls that never touched the gateway. Kapālins reads those events with a read-only key and puts them in the same timeline, incident queue and evidence chain as the gateway verdicts.
- InvokeModel and streamed invocations recorded as AI requests
- Model-access and admin changes flagged
- The raw CloudTrail record kept as AWS returned it
One endpoint, one key, every provider.
Point the application at your gateway host with a virtual key. Kapālins routes to Amazon Bedrock with the key it holds, fails over when Amazon Bedrock is down, and meters every call to the team that made it.
- Your app speaks OpenAI or Anthropic API format at the gateway; Bedrock InvokeModel on the way out
- 87 Amazon Bedrock models priced, so spend lands on a team the same day
- Block the provider domains at your firewall and this becomes the only way out
A blocked Bedrock call, opened.
Open any Bedrock call in Logs and Kapālins shows who called, the model it was headed for, what was inspected and which guardrail stopped it, before the prompt reached your AWS account.
- A scrubbed preview or only a SHA-256 hash, your choice
- The caller’s recent history beside the verdict
- The same record feeds incidents, your SIEM and the evidence pack
CloudTrail, in the same timeline.
A data scientist calling Claude on Bedrock from a notebook never touches the gateway, but CloudTrail still records it. Kapālins reads those events and sets them beside the gateway’s verdicts, attributed to the IAM principal that made them.
- Read-only: cloudtrail:LookupEvents, nothing written back
- Source label on every row
Agents calling Amazon Bedrock, fingerprinted.
Every agent and service key that calls Amazon Bedrock through the gateway gets a behaviour baseline: calls, active hours, models, prompt repetition, injection rate. When one drifts it is flagged with the reasons, and one click drafts a guardrail or quarantines the key.
- The tools and MCP servers each agent actually invoked
- Detect only by default; quarantine is one click and reversible
Every Amazon Bedrock model, approved or not.
The Probe Runner, the garak red team and Alignment Lab test each model you use, through your own key. A model is approved, conditional or blocked, and Policy Shield enforces the verdict at the gateway.
- Injection, unsafe code, harmful behaviour and hallucination suites
- A critical finding holds new use until someone approves it
Four steps.
- Create an IAM key for KapālinsAllow bedrock:InvokeModel and bedrock:ListFoundationModels, then create an access key.
- Add Amazon BedrockIntegrations › Amazon Bedrock › paste the key, secret and region. Kapālins lists your models live, then seals the key.
- Point applications at the gatewayA base URL and a virtual key. Request and reply formats stay as they are.
- Add AWS CloudTrailA read-only key with cloudtrail:LookupEvents, for the Bedrock calls that skip the gateway.
See Amazon Bedrock governed in thirty minutes.
Bring the person who holds the credential. We connect it live and watch the first events land.
Questions buyers ask.
Does the gateway add latency to Amazon Bedrock calls?
Policy Shield runs in the request path. Each family can be set to detect only, and the gateway reports its own added time per call in the timeline.
Do my applications need code changes?
A base URL and a key. The gateway accepts the OpenAI and Anthropic formats, so request and response handling stay as they are.
Can Amazon Bedrock be governed without the gateway?
Routing is what makes inline control possible. AI that cannot be routed, such as hosted copilots, is governed from its audit logs, identity grants and the device sensor instead.