
Argent for Amazon Bedrock SDKs
Bedrock calls go through Argent, which signs them with a brokered AWS credential your app never holds. Here is what Argent governs, how it connects and what your team sets.
What Argent does with Amazon Bedrock SDKs
Every model call an app makes with Amazon Bedrock SDKs goes through Argent first. Argent knows which agent sent it and which person owns that agent, checks it against your policy, and writes a signed record of what it decided.
- A named agent with a human owner. Each app or service you connect uses its own Argent agent key, tied to an accountable person, so no call is anonymous. Identity tethering
- Only the models you allow. The agent can reach only the providers and models your policy names, and a request can be swapped to an approved model. Model control
- Sensitive data handled before it leaves. Prompts and replies are scanned for personal and secret data, then redacted or blocked as your policy says. Sensitive data redaction
- Spend priced and capped. Every request is priced and metered against budgets for the agent, its owner and the teams above them. AI spend caps
- A signed record you can replay. Each decision becomes a hash-chained, signed audit record, and requests are grouped into sessions you can replay. Session replay
How Amazon Bedrock SDKs connect
Amazon Bedrock SDKs reach Argent in two ways.
- Gateway base URL. The app points its Bedrock endpoint at your Argent route with an Argent agent key. Argent signs the request with a brokered AWS credential, so the app never holds AWS keys.
- TLS-inspecting forward proxy. Your app keeps its normal Amazon Bedrock SDKs settings and sends its HTTPS traffic through the Argent forward proxy and trusts your Argent certificate; the exact settings are below. The proxy signs in with the agent's own key, so every call is attributed, then runs the same checks as the gateway. It opens only known AI hosts, and its certificate is limited to those hosts.
Proven with the real tool. Argent's team has driven Amazon Bedrock SDKs themselves through a live Argent gateway and checked the signed records it produced.
The same steps are in the Argent console under Integrations > AI Clients, and each agent's Connect tab gives the copy-paste values for your tenant.
What you configure
What your team sets in Amazon Bedrock SDKs. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Gateway route. POST https://<ARGENT_GATEWAY>/<tenant>/bedrock/model/<modelId>/converse-stream with Authorization: Bearer <an Argent agent key> and Host = bedrock-runtime.<region>.amazonaws.com or the gateway's own public name. The agent holds no AWS credentials.
- Forward proxy. Forward-proxy mode (no URL change): HTTPS_PROXY=http://<user>:<ARGENT_AGENT_KEY>@<ARGENT_PROXY_HOST> plus trust of the tenant intercept CA. The tenant must have the forward proxy enabled and the vendor host registered as an upstream. AWS SDKs honour HTTPS_PROXY and AWS_CA_BUNDLE.
- Trust the CA. AWS_CA_BUNDLE=/path/argent-ca.pem (plus the Argent CA in the system store).
Make Argent the only path
Make Argent the only path for Amazon Bedrock SDKs. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Bedrock IAM / SCP: only the Argent gateway may invoke models. Humans and apps with AWS credentials cannot call Bedrock directly. Vendor docs
- Service-specific endpoint override. Default every AWS SDK in the fleet to the Argent endpoint. Vendor docs
- Machine-wide environment variables (Windows). Sets the base URL / proxy / CA variables for every process on the machine so SDK-based apps default to Argent. Vendor docs
- Managed environment (macOS). Same variables for GUI-launched and shell processes. Vendor docs
- Service / container environment (Linux, Kubernetes, CI). Sets the variables where most production SDK code runs. Vendor docs
Same settings everywhere it runs. The Argent fleet setup script and certificate bundle give every service, container and build runner the same proxy and certificate settings.
Want to see which AI tools people already run before you push anything? Start with Shadow AI discovery in watch mode. Watch before you enforce
Check that it works
Send one request and look for the signed row. Signed LLM ALLOW row for the bedrock route in the Argent console live stream; with a blocked prompt, a signed deny row.
Every request also appears on the live stream with the agent's name and owner, and in the session view. Session replay
Where to go next
Keep going. Pages that cover the same ground from another angle.
- Use case: Governing customer-facing AI assistants
- Use case: Controlling agent tool access: MCP and agent-to-agent
- Goals: See all AI in your company, Data loss prevention, Budget and token spend, Model control and routing, Agent identity and ownership
- Capabilities: Keyless agents, Prompt injection defense, Response screening, One-click audit evidence
- Related integrations: Salesforce Agentforce, ServiceNow Now Assist, OpenAI SDKs, Anthropic SDKs
- All integrations: Browse every AI client, provider, vault and identity source
Want this running on your own use cases?
Book a demo