Amazon Bedrock #
On this page
Use the models in your company's AWS account through Amazon Bedrock: Claude, Amazon Nova, Llama, Mistral and the others Bedrock offers. Requests are signed with your own AWS credentials and billed to your AWS account under your AWS agreement. Maple stores no AWS key: on a laptop it uses your AWS profile or SSO sign-in, and on Kubernetes the pod's IAM role.
Follow AWS's terms and each model provider's terms. AWS makes the account holder responsible for the people who use the service through the account.
In plain words #
- What it is. Claude, Amazon Nova, Llama and the other models in your company's AWS account, through Amazon Bedrock, billed to that account.
- Why you want it. No new key: Maple signs each request with the AWS sign-in you already have (a profile, SSO, or the pod's role on Kubernetes).
- What to do. Sign in to AWS as usual, then
maple-proxy bedrock modelsto see what your region offers andmaple-proxy bedrock addto add it. The provider then appears on the setup page's Providers tab, where Edit changes it.
On a laptop #
Sign in to AWS the way you already do, then add Bedrock to the proxy:
aws sso login --profile work # or any other way the AWS CLI finds credentials
maple-proxy bedrock models --profile work --region us-east-1
maple-proxy bedrock add --profile work --region us-east-1 \
--model us.anthropic.claude-sonnet-4-5-20250929-v1:0 --model anthropic.claude-opus-4-7
bedrock models lists the text models and inference profiles the region offers your account, and which Bedrock API
the proxy uses for each. bedrock add checks the models you name against that list and writes the provider into
config.yaml (a running proxy picks it up at once). The entry it writes:
providers:
- id: bedrock
type: bedrock
bedrock:
region: us-east-1 # default: the region your AWS configuration names (AWS_REGION or the profile's)
profile: work # default: the AWS default chain
models:
- id: us.anthropic.claude-sonnet-4-5-20250929-v1:0
context_window: 200000
supports_tools: true
- id: anthropic.claude-opus-4-7
context_window: 200000
supports_tools: true
On the setup page, Add provider with the type Amazon Bedrock works too: type the model ids. The region and
profile live in the bedrock: section of the raw configuration (the form keeps them when you edit the provider).

maple-proxy bedrock add (a demo setup, with a stand-in for Amazon Bedrock).
Where the credentials come from #
The proxy uses the AWS SDK's own credential chain, in its usual order, and the SDK refreshes temporary credentials before they expire:
- Environment variables:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_SESSION_TOKEN, orAWS_PROFILE. - The shared files
~/.aws/configand~/.aws/credentials: a profile (bedrock.profile), an IAM Identity Center (SSO) profile,credential_process. - Web identity:
AWS_WEB_IDENTITY_TOKEN_FILEandAWS_ROLE_ARN(IAM roles for service accounts on EKS). - The container credentials endpoint: ECS tasks, and EKS Pod Identity.
- The EC2 instance's role.
bedrock.role_arn assumes a role with whatever the chain found, for every request of that provider. A Bedrock API
key in AWS_BEARER_TOKEN_BEDROCK is used instead of signing, as AWS's own tools do, and only over https.
When the sign-in runs out (an expired SSO session, say), requests to that provider fail as not authorised and the
setup page's provider list says that no usable AWS credentials were found. Run aws sso login again; nothing needs a
restart.
A fixed access key, only if you must: put it in the environment and run
maple-proxy bedrock store-key --id bedrock
It keeps the key in the secret store and writes only references into config.yaml
(access_key_id: ${secret:provider/bedrock/aws_access_key_id} and the same for secret_access_key). A key written
into the file itself is refused.
Permissions #
The identity needs bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream on the models (and on the
inference profiles you use), plus bedrock:ListFoundationModels and bedrock:ListInferenceProfiles for bedrock
models and bedrock add.
Model access #
A model must be available to your AWS account in the region before it answers. Some model providers ask for a one-time use-case form or an AWS Marketplace subscription first; open the Amazon Bedrock console in that region to check. Until then, requests fail as not authorised, and the message names the model, the region and the console link. Other models on the same provider keep working.
Regions and inference profiles #
One provider is one region with one set of credentials: an account in Maple's sense. Several regions are several providers:
maple-proxy bedrock add --region us-east-1,us-west-2 --model us.anthropic.claude-sonnet-4-5-20250929-v1:0
This writes bedrock-us-east-1 and bedrock-us-west-2 and chains them with