Bedrock

Bedrock agents invoke action groups over HTTP. Faramesh's HTTP proxy sits in front of your action group endpoint, every call is evaluated by the daemon before it forwards to the real handler (Lambda, ECS, anything serving the Bedrock OpenAPI schema).

Tier: HTTP proxy. Latency overhead: 5–15 ms per call.

Wiring

Bedrock agent  →  Faramesh HTTP proxy  →  Action group handler (Lambda)
                         ↓
                 policy engine, WAL, providers

Set up

import "github.com/faramesh/faramesh-registry/frameworks/bedrock@1.0.0"

runtime {
  mode        = "enforce"
  http_listen = "0.0.0.0:8443"
}

agent "bedrock-ops" {
  default deny

  rules {
    permit lookup_customer
    defer  refund_order if amount >= $100
    permit refund_order if amount <  $100
    deny   delete_customer
  }

  rate_limit "*": 200 per minute
}

runtime {
  http_listen   = "0.0.0.0:8443"
  http_upstream = "https://lambda-url.example.com"
}

OpenAPI

Faramesh reads the Bedrock action group OpenAPI document to map paths and parameters to tool names. The operation operationId becomes the tool id in policy:

paths:
  /customers/{id}:
    get:
      operationId: lookup_customer
  /orders/{id}/refund:
    post:
      operationId: refund_order

Conditions in policy reference parameters by name (amount, id, etc.):

permit refund_order if amount < $100

TLS

The proxy terminates TLS on its listener. Provide certs via runtime:

runtime {
  http_listen   = "0.0.0.0:8443"
  tls_cert_file = "/etc/faramesh/server.crt"
  tls_key_file  = "/etc/faramesh/server.key"
}

What's next

• Stack reference → enforcement
• Providers. AWS Secrets Manager, KMS, audit sinks
• Denial codes