Skip to main content
watch_bedrock wraps a boto3 bedrock-runtime client’s converse method. It is duck-typed, so the Sakshi SDK does not depend on boto3: it wraps the client you already build. Bedrock in the AWS Mumbai region is the residency-compliant hosted path for Indian regulated entities, so the modelId captured here is para-56 evidence on the deployment most partners will actually run.

Install

Wrap the client

See the shared shape for how sakshi and agent_id are created.

What gets recorded

Each Converse call inside a witness session lands an llm_call step, and the served model identity auto-fills (para-56):
  • The provider, recorded as aws-bedrock.
  • The requested modelId.
  • The stop reason.
  • Input and output token usage.
  • The call latency.
  • With content capture on, the last message you sent and the first text block of the response, each truncated to content_limit.

Capture options

  • capture_content defaults to True. Content capture is safe by design: the platform tokenizes PII at ingest, before storage or hashing. Set it to False for a minimal-capture deployment where only metadata, tokens, and identity are recorded.
  • content_limit caps how much of each message and response is stored. The default is 1000 characters.
A call made outside a witness session passes through untouched and is not recorded. Recording is fail-open: it never breaks or delays the Converse call.

Full SDK reference

The client, the witness session, and enforcement.