Mach11 Connect
Bedrock Proxy in Your Account
Deploy a Bedrock proxy Lambda directly into your AWS account. Get your API key and endpoint from CloudFormation Outputs — no third-party access, no data sharing.
Deploy Now →Up and running in 3 steps
Deploy CloudFormation
Run our one-click stack in your AWS account. It deploys the proxy Lambda and creates your Bedrock API key automatically.
Copy Keys from Outputs
Open the CloudFormation Outputs tab. Copy your Bedrock API key and Lambda proxy URL — that's all you need.
Start Building
Plug the URL and key into Claude Code, Cursor, or any SDK. Every request goes directly to Bedrock in your account.
Runs in Your Account
The proxy Lambda lives in your AWS account. Requests never leave your infrastructure.
Native Bedrock API Key
Uses AWS's native Bedrock API key — no IAM credentials to manage, no SigV4 signing required.
Instant Setup
One CloudFormation stack, two Outputs, done. Works with Anthropic SDK, OpenAI SDK, Claude Code, and Cursor.
Why Mach11 Connect
No data sharing
All requests stay within your AWS account — we never see your traffic
Your keys, your control
API key lives in your account, created by your CloudFormation stack
Multi-model access
Claude, Kimi, Minimax — all Bedrock foundation models in one endpoint
OpenAI compatible
Drop-in replacement for the OpenAI API — use any OpenAI SDK client
Streaming support
Full SSE streaming for both Anthropic and OpenAI API formats
Never-expiring keys
Create long-term Bedrock API keys — no forced rotation
🔒 Your account • 🏢 Your keys • 🚀 Your infrastructure