cat ~/.openclaw/openclaw.json | jq -r .models{
"mode": "merge",
"providers": {
"bedrock": {
"baseUrl": "https://bedrock-runtime.us-east-1.amazonaws.com",
"apiKey": "${AWS_BEARER_TOKEN_BEDROCK}",
"api": "bedrock-converse-stream",
"auth": "api-key",
"authHeader": true,
"models": [
{
"id": "openai.gpt-oss-120b-1:0",
"name": "GPT OSS",
"reasoning": true,
"input": [
"text"
],
"cost": {
"input": 0,
"output": 0,
"cacheRead": 0,
"cacheWrite": 0
},
"contextWindow": 262144,
"maxTokens": 8192
}
]
}
}
}% cat ~/.openclaw/openclaw.json | jq -r .agents.defaults{
"model": {
"primary": "bedrock/openai.gpt-oss-120b-1:0"
},
"models": {
"bedrock/openai.gpt-oss-120b-1:0": {
"alias": "gpt-oss-120b"
}
},
...
}# generate Bedrock API KEY at https://console.aws.amazon.com/bedrock/home#/api-keys
export AWS_BEARER_TOKEN_BEDROCK=xxxxxxxxx
openclaw gateway run --verbose // make sure no errorsNow when you type /new in Telegram, you should see
✅ New session started · model: bedrock/openai.gpt-oss-120b-1:0Then it works!
Hi everyone,
When I try to connect to AWS Bedrock via API, I keep getting the following error:
ThrottlingException
Too many tokens per day, please wait before trying again.
This is a brand-new AWS account, and I haven't actually been able to make a single successful request yet.
I originally assumed Bedrock would work on a pay-as-you-go basis, where usage is simply charged per token.
However, after searching online, I found many different explanations and suggested fixes, and I'm still not sure which configuration is actually correct or what needs to be enabled for a new account.
Has anyone experienced this with a new account?
Is there any quota, approval step, or default limit that needs to be adjusted before Bedrock API calls will work properly?