# AWS Bedrock

> Use your AWS Bedrock account through DigitSpace with a Bedrock API key or an IAM access key, in any of 15 AWS regions.

Source: https://digitspace.ai/docs/keys/aws-bedrock · Last checked: 2026-10-31

There are two Bedrock providers in the list:

- **AWS Bedrock** uses Bedrock's Converse API.
- **AWS Bedrock (OpenAI-compatible)** uses Bedrock's OpenAI-compatible endpoint.

Both take the same credentials.

## Credentials

Either:

- a **Bedrock API key**, created in the Bedrock console; or
- an **IAM access key**, pasted as `accessKeyId:secretAccessKey`. Temporary credentials work as `accessKeyId:secretAccessKey:sessionToken`. The access key ID starts with `AKIA` or `ASIA`.

The identity needs permission to invoke the models you'll use, and the models must be enabled for your account in that region.

## Steps

1. In **Provider keys → Add a provider key**, choose **AWS Bedrock**.
2. Paste the key, and choose the **Region** your models are enabled in (`us-east-1` by default).
3. Save.

## What it serves

Your Bedrock key serves the models DigitSpace's catalogue routes to Bedrock. Check them under [Providers](/providers). Bedrock doesn't give DigitSpace a model list, so other models aren't added automatically. On Enterprise you can add them as custom models.

## Limits of the Converse API

- Images must be sent as `data:` URLs (PNG, JPEG, GIF or WebP), not web addresses.
- `response_format`, `n`, `seed` and other fields Converse doesn't have are dropped.
- `reasoning_effort` becomes a thinking budget for Claude models only.

See [Chat Completions](/docs/api/chat-completions#how-the-request-reaches-the-provider).