AWS + Bedrock, the validated path
Amazon Bedrock on your own credentials; IAM-scoped workers in private subnets with no general egress.
Controls evidenced
Use cases
Each path ends in evidence you can hand a control owner, and names the controls it evidences. Pick the one closest to your first audit question.
8 use cases · 4 available today
Amazon Bedrock on your own credentials; IAM-scoped workers in private subnets with no general egress.
Controls evidenced
One install command adds recording hooks; every session emits signed, schema-versioned activity events.
Controls evidenced
Unattended agents pause for portal approval; if the portal is unreachable, the action is denied.
Controls evidenced
Narratives for SR 11-7, FFIEC, DORA (EU operational resilience), EU AI Act, ISO 42001, and SOC 2, backed by records your engineers already produce.
Controls evidenced
Every mapped control
In the pull request itself: which sessions produced the change, what was approved, whether rationale is on record.
Controls evidenced
Hash-bound JSON or zip packages a local verifier checks offline — no raw prompts or source inside.
Controls evidenced
OS-enforced file, network, and process boundaries for MCP servers, under the same governance rules.
Roadmap target · not evidence today
A scripted pass in your account: ingest, approvals, Agent Run Audit, PR evidence, worker dispatch, audit-chain verification.
Roadmap · not evidence today
Would close the customer-cloud validation gap in every mapping
Don’t see your workflow?
Start with the AWS walkthrough; we’ll map your control owners onto the same evidence pack.