📝 falg23043 reroutes Mike's AI through AWS Bedrock 2 commits 3mo ago infrastructureintegration draft
The fork swaps the model where every user brings their own Anthropic key for a single, centralised AWS-hosted setup.
falg23043/mike
falg23043/mike - firm-hosted Bedrock deployment, drops per-user Anthropic API keys
falg23043's fork has one recorded topic: replacing the direct Anthropic API with AWS Bedrock. The intent is a firm-hosted deployment where server-side AWS credentials cover all Claude access and users manage no API keys themselves. The adapter is functionally complete but includes a debugging artifact (unconditional disk logging to bedrock-raw-stream.log) that is not production-safe, and a suspect model ID for Opus 4.6 that doesn't match Bedrock's versioned naming format.
The migration drops user_profiles.claude_api_key destructively. BEDROCK.md documents the changes and remaining TODOs specific to this deployment; it shouldn't carry over into a general adoption of the adapter.
What's in it
- Firm-hosted deployment model Reshapes Mike from a bring-your-own-key tool into something a single team can stand up and share.
- AWS Bedrock as the Claude provider Routes model calls through Bedrock, which matters for shops that already run their AI workloads in AWS.
Direction
infrastructuremulti-tenant
Activity
Threads of work (detailed view)
falg23043 reroutes Mike's AI through AWS Bedrock
The fork swaps the model where every user brings their own Anthropic key for a single, centralised AWS-hosted setup.
falg23043 swaps per-user Anthropic keys for AWS Bedrock server-side credentials
falg23043 converted Mike from a bring-your-own-API-key tool to a firm-hosted deployment by replacing the direct Anthropic API with AWS Bedrock. Users no longer manage any Claude credentials; the firm's AWS account covers it.