AWS Bedrock (gateway)

1
{
2
  "mcpServers": {
3
    "respan-docs": {
4
      "url": "https://mcp.respan.ai/mcp/docs"
5
    }
6
  }
7
}

Use Respan Gateway to call AWS Bedrock models while keeping unified observability (logs, cost, latency, and reliability metrics) in Respan.

Prerequisites

• A Respan API key
• AWS Bedrock credentials (BYOK)

Supported SDKs / integrations

Configuration

There are 2 ways to add your AWS Bedrock credentials to your requests:

Via UI (Global)

1

Navigate to Providers

Go to the Providers page. This page allows you to manage credentials for supported model providers.

2

Add your AWS Bedrock credentials

Select AWS Bedrock and add the required credential fields.

• aws_access_key_id — your AWS access key ID
• aws_secret_access_key — your AWS secret access key
• aws_region_name — the AWS region where Bedrock is enabled

3

Choose available models (Optional)

Copy the model ID from the Respan Models page, paste it into the available models field, and press Enter. Leave the field empty to apply the credentials to all AWS Bedrock models.

4

Configure Load Balancing (Optional)

Add multiple AWS Bedrock credential sets for redundancy. Use the Load balancing weight field to control traffic distribution.

Via code (Per-Request)

You can pass credentials dynamically in the request body. This is useful if you need to use your users’ own API keys (BYOK).

Add the customer_credentials parameter to your Gateway request:

1
{
2
  "customer_credentials": {
3
    "bedrock": {
4
      "aws_access_key_id": "YOUR_AWS_ACCESS_KEY_ID",
5
      "aws_secret_access_key": "YOUR_AWS_SECRET_ACCESS_KEY",
6
      "aws_region_name": "us-east-1"
7
    }
8
  }
9
}

Override credentials for a particular model (Optional)

Use credential_override when one request or model should use different credentials than the default provider key.

1
{
2
  "customer_credentials": {
3
    "bedrock": {
4
      "aws_access_key_id": "YOUR_AWS_ACCESS_KEY_ID",
5
      "aws_secret_access_key": "YOUR_AWS_SECRET_ACCESS_KEY",
6
      "aws_region_name": "us-east-1"
7
    }
8
  },
9
  "credential_override": {
10
    "bedrock/anthropic.claude-3-5-sonnet-20240620-v1:0": {
11
      "aws_access_key_id": "ANOTHER_AWS_ACCESS_KEY_ID",
12
      "aws_secret_access_key": "ANOTHER_AWS_SECRET_ACCESS_KEY",
13
      "aws_region_name": "us-west-2"
14
    }
15
  }
16
}

Supported models

Find the complete and current list of AWS Bedrock model IDs on the Respan Models page. Use the exact model ID shown there in your gateway requests.

Log AWS Bedrock requests

If you are not using the Gateway to proxy requests, you can still log your AWS Bedrock requests to Respan asynchronously. This lets you track cost, latency, and performance metrics for external calls.

1
import requests
2
3
url = "https://api.respan.ai/api/request-logs/create/"
4
payload = {
5
  "model": "bedrock/anthropic.claude-3-5-sonnet-20240620-v1:0",
6
  "prompt_messages": [
7
    {
8
      "role": "user",
9
      "content": "Hello, how are you?"
10
    }
11
  ],
12
  "completion_message": {
13
    "role": "assistant",
14
    "content": "Hello from AWS Bedrock through Respan."
15
  },
16
  "cost": 0.001,
17
  "generation_time": 1.2,
18
  "customer_params": {
19
    "customer_identifier": "user_123"
20
  }
21
}
22
headers = {
23
    "Authorization": "Bearer YOUR_RESPAN_API_KEY",
24
    "Content-Type": "application/json",
25
}
26
27
response = requests.post(url, headers=headers, json=payload)