# AWS Bedrock

---

The AWS Bedrock provider routes agent LLM calls through **Amazon Bedrock in your own AWS account** instead of a vendor API key.

## Why Bedrock

- **No API key to manage.** There is nothing to paste and no secret stored on the Deployment.io side — selecting the provider is the configuration.
- **Billing through AWS.** Model usage lands on your existing AWS bill, alongside the infrastructure your runner already manages.
- **Your account boundary.** Prompts and completions flow through Bedrock in your own AWS account and region — they never transit a vendor account you don't control.

## Enabling Bedrock

1. In the dashboard, go to **Organization Settings → Agents → LLM Providers**.
2. On the **AWS Bedrock** card, click **Enable AWS Bedrock**.

That's the whole setup — there is no credential to enter. When an agent job starts, your runner issues short-lived, narrowly scoped AWS credentials to the sandboxed agent container, and the agent calls models served by Bedrock in your runner's region. There are no long-lived keys to rotate or leak.

## Requirements

| Requirement                   | Why                                                                                 |
| ----------------------------- | ----------------------------------------------------------------------------------- |
| Your own AWS runner           | The runner issues the scoped credentials the agent uses.                            |
| Bedrock model access          | Claude models must be enabled in Bedrock in your runner's region.                   |
| Claude Code or opencode agent | Bedrock serves the Claude Code and opencode agents; the Codex agent is OpenAI-only. |

## Disabling

Click **Remove** on the AWS Bedrock card. If no other provider is configured afterwards, Task creation is blocked until one is.

## Troubleshooting

- **A Task fails with an access or authorization error** — Claude model access is probably not enabled in Bedrock in your runner's region. Enable it in the AWS console under **Bedrock → Model access** and re-run.
- **A model you expected isn't available** — model availability on Bedrock can trail the direct Anthropic API, and varies by region. A newly released model may take time to appear in your runner's region.

---

Source: https://deployment.io/docs/ai-providers/aws-bedrock/