Amazon Bedrock
OpenDocBot talks to Amazon Bedrock through the Converse API on bedrock-runtime, authenticated with a Bedrock API key (a bearer token). No AWS SDK, SigV4 signing, or long-lived IAM secret is involved.
Setup:
- In the AWS Console, open Amazon Bedrock and enable the models you need in your target Region (model access is per-region).
- Create a key under Bedrock -> API keys.
- Preset: Amazon Bedrock
- Enter the Region id the key was created for (for example
eu-north-1), then paste the API key. - Pick a model (or Custom model ID), Test Connection, Apply.
The runtime endpoint is derived from the region: https://bedrock-runtime.<region>.amazonaws.com.
API keys. Short-term keys start with bedrock-api-key-, last up to 12 hours, and only work in the Region that created them (safest). Long-term keys start with ABSK, work in any Region, and are meant for exploration — prefer short-lived keys or a managed deployment, and rotate regularly. The default AmazonBedrockLimitedAccess policy is enough; narrower keys need bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream.
Models. The list is fetched from Bedrock (ListFoundationModels / ListInferenceProfiles) and shows only ACTIVE, text-output, Converse-capable models. Profile-only models appear by their profile ID (for example eu.anthropic.claude-sonnet-4-6). If discovery fails the add-in falls back to /v1/models and a small static list; use Custom model ID for anything missing (for example a wrong or Region-specific model returns 404).
Account not authorized
A 403, "Your account is currently being verified.", or 400 NOT_AUTHORIZED means the AWS account is not yet authorized for Bedrock — not a key or model-access problem. New accounts usually clear this in a few hours. A persistent NOT_AUTHORIZED (check with aws bedrock get-foundation-model-availability --region <region> --model-id <model-id>) has no self-service fix: open an AWS Support case under Account and billing asking to complete Bedrock account verification.
Browser blocked (CORS)
If the taskpane cannot call Bedrock directly, enable Proxy API requests through this server (self-hosted / dev deployments) to route the request through the same-origin /proxy/ endpoint.
Prompt caching, key storage, and reasoning are covered in Providers and Configuration.