Add AWS Bedrock Converse/ConverseStream provider support #255

CsBigDataHub · 2026-01-04T19:11:41Z

Hello @ericdallo,

This commit implements full support for AWS Bedrock's Converse and ConverseStream APIs in ECA.

Key Features:

Standard chat completions via Converse API
Streaming responses via ConverseStream API
Full tool use support with proper formatting
Custom binary event stream parser (no AWS SDK required)
Bearer token authentication via external proxy
Model aliasing for convenience
Support for additional model parameters (e.g., top_k, topP)

Implementation Details:

Custom binary stream parser following AWS Event Stream protocol
Proper CRC checksum handling for streaming responses

Testing:

8 tests covering all major functionality (17 assertions)
Tool use workflows
Binary stream parsing
Response parsing
Payload building

Files Changed:

src/eca/llm_api.clj: Added require for aws-bedrock provider
src/eca/llm_providers/aws_bedrock.clj: New provider implementation
test/eca/llm_providers/aws_bedrock_test.clj: Comprehensive test suite
⚠️ ignore AWS_BEDROCK_EXAMPLE.md: Usage documentation, will be remove or merged to models documentation page before merge ⚠️

Will add to add to the changelog once I am able to test, my company proxy and cloudflare seems to be blockers at this point.

I added a entry in changelog under unreleased section.

This commit implements full support for AWS Bedrock's Converse and ConverseStream APIs in ECA. Key Features: - Standard chat completions via Converse API - Streaming responses via ConverseStream API - Full tool use support with proper formatting - Custom binary event stream parser (no AWS SDK required) - Bearer token authentication via external proxy - Model aliasing for convenience - Support for additional model parameters (e.g., top_k, topP) Implementation Details: - Uses hato.client for HTTP requests (consistent with other providers) - Custom binary stream parser following AWS Event Stream protocol - Proper CRC checksum handling for streaming responses - Comprehensive error handling and logging Testing: - 8 tests covering all major functionality (17 assertions) - Tool use workflows - Binary stream parsing - Response parsing - Payload building Configuration Example: ```clojure {:providers {:bedrock {:api "bedrock" :key "${env:BEDROCK_API_KEY}" :url "https://proxy.example.com/model/{modelId}/converse" :region "us-east-1" :models {:claude-3-sonnet {:modelName "anthropic.claude-3-sonnet-20240229-v1:0"}}}}} ``` Usage: ```clojure ;; Standard request (provider/request bedrock-config messages {:temperature 0.5 :top_k 200}) ;; With tools (provider/request bedrock-config messages {:tools [tool-spec] :temperature 0.7}) ;; Streaming (provider/request bedrock-stream-config messages {:temperature 0.7}) ``` Files Changed: - src/eca/llm_api.clj: Added require for aws-bedrock provider - src/eca/llm_providers/aws_bedrock.clj: New provider implementation - test/eca/llm_providers/aws_bedrock_test.clj: Comprehensive test suite - AWS_BEDROCK_EXAMPLE.md: Usage documentation This implementation follows the established patterns in the codebase and is ready for production use. 🤖 Generated with [eca](https://eca.dev) Co-Authored-By: eca <noreply@eca.dev>

CsBigDataHub · 2026-01-04T19:19:03Z

Future feature request -

This Implementation uses Bearer token retrieved externally but we can support AWS Bedrock requires SigV4 signing. Right now I have python code to perform single sign on and retrieve the token which I intend to use here.

See here - karthink/gptel#1200 (comment)

We can add AWS SigV4 signing directly (using a library like cognitect/aws-api) but we need to add aws library. I have conflicting thoughts on this one.

CsBigDataHub · 2026-01-04T19:21:38Z

Maybe we can leverage this after merge - #249.
exactly what I am doing with python.

ericdallo · 2026-01-08T13:53:43Z

src/eca/llm_providers/aws_bedrock.clj

+
+(defn message->bedrock [msg]
+  (case (:role msg)
+    "tool"


is this really working? it should be tool_call right?

Also there are messages missing like reason, ref

ericdallo · 2026-01-08T13:54:38Z

@CsBigDataHub is this really ready to be reviewed or you are working on it? taking a quick look it seems to be missing features, llm-api integration etc

CsBigDataHub · 2026-01-08T14:20:00Z

Hi @ericdallo , no it is not ready, I need more time.
It on back burner right now. Bit busy at the moment, will get back to it in a weeks time.

jumarko · 2026-01-08T21:37:07Z

src/eca/llm_providers/aws_bedrock.clj

+   This implementation uses Bearer token authentication, which requires
+   an external proxy/gateway that handles AWS SigV4 signing.


What is this "external proxy" thing?
Won't the implementation work with standard Bedrock APIs, such as https://bedrock-runtime.eu-west-2.amazonaws.com/model/<model_id>/converse ?

Will work, but you will need to get the token and configure it.

Yeah, I assumed that the user will create a Bedrock API token first.

But what's the difference when using proxy? Is that for cases when the user has configured their aws credentials on their machine but has no explicit Bedrock API token?

Nothing really, except for the URL, endpoints will be the same.

Adds a new test case to verify parsing of event stream containing both text and tool call events, ensuring correct extraction of content and tool use details.

Convert keyword values to strings while preserving nested structures during JSON parsing to ensure consistent output format. This change ensures that keyword-based fields (like :toolUseId, :status, etc.) are properly serialized as strings in the final event structure, aligning with expected JSON output formats in AWS Bedrock responses. The update is applied in both the parser and test cases to validate the behavior with tool calls and content deltas, ensuring correct field access using string paths (e.g., [:toolResult :toolUseId]) instead of keywords.

CsBigDataHub · 2026-01-18T20:30:54Z

@ericdallo, I was finally able to establish connection to AWS Bedrock from my company proxy but tools are not supported from our company API gateway

{
"detail": {
"statusCode": 400,
"message": "Currently tools are not supported in AI-Gateway for AWS hosted models."
}
}

Unfortunately, I will not be able to test this. I can close the PR and pick up the work once I have full access to AWS Bedrock models.

Let me know what would you like me to do.

jumarko · 2026-01-20T16:12:16Z

Regarding testing:

Unfortunately, I will not be able to test this. I can close the PR and pick up the work once I have full access to AWS Bedrock models.

Let me know what would you like me to do.

I should be able to test this (given enough instructions :)) using our own aws account - we don't use a proxy, just it's direct calls to Bedrock APIs.

- Integrate AWS Bedrock provider into provider->api-handler dispatch mechanism - Enhance build-endpoint function to support multiple URL patterns: * Base URL pattern (recommended): https://api.company.com/model/ * Standard AWS pattern: auto-generates bedrock-runtime URLs - Add support for region-prefixed model IDs in URL construction - Enhance streaming tool call support with proper event parsing - Add comprehensive tests for URL construction and streaming tool calls - Update documentation with configuration examples and usage patterns - Ensure full compatibility with AWS Bedrock Converse and ConverseStream APIs

- Changed documentation from "three URL configuration patterns" to "two patterns" - Renamed "Base URL (Recommended)" to "Custom Proxy URL (Recommended)" - Removed "Legacy Placeholder URL" section and related test - Simplified URL construction logic to only support: 1. Custom proxy URL (base URL with region.modelId/suffix) 2. Standard AWS Bedrock URL (requires region) - Removed legacy placeholder replacement logic and test case The change aligns the documentation and code with current functionality, removing deprecated backward-compatible patterns.

- Add detailed configuration examples for proxy and non-proxy setups - Include multi-region configuration example - Enhance authentication section with clear options - Add comprehensive troubleshooting guide - Include URL construction verification examples - Document both production and development use cases

- Add clear Converse vs ConverseStream API documentation - Document stream parameter behavior and defaults - Provide explicit examples for both synchronous and streaming modes - Add API endpoint selection flowchart - Clean up configuration examples to be more focused - Document URL generation patterns for each mode - Improve parameter documentation with endpoint mapping

CsBigDataHub · 2026-01-24T17:06:10Z

@jumarko,

please check out my fork and use this branch - feature/support-aws-bedrock-provider

If you have clojure and Babashka installed, create a eca executable with bb prod-cli.
Place it in a location where your system can see it.
Do not forget to remove any old eca executable.
configure AWS bedrock token to BEDROCK_API_KEY or whatever name you like.

example AWS Bedrock config

{
  "providers": {
    "bedrock": {
      "api": "bedrock",
      "key": "${env:BEDROCK_API_KEY}",
      "region": "us-west-2",
      "models": {
        "claude-3-sonnet": {
          "modelName": "anthropic.claude-3-sonnet-20240229-v1:0"
          // Uses /converse-stream by default
        }
      }
    }
  }
}

Generated URL: https://bedrock-runtime.us-west-2.amazonaws.com/model/us-west-2.anthropic.claude-3-sonnet-20240229-v1:0/converse-stream

Explicit Converse Configuration

{
  "providers": {
    "bedrock": {
      "api": "bedrock",
      "key": "${env:BEDROCK_API_KEY}",
      "region": "eu-west-1",
      "models": {
        "cohere-command-r": {
          "modelName": "cohere.command-r-v1:0",
          "extraPayload": {
            "stream": false  // Force /converse endpoint
          }
        }
      }
    }
  }
}

Generated URL: https://bedrock-runtime.eu-west-1.amazonaws.com/model/eu-west-1.cohere.command-r-v1:0/converse

Let me know if you have any questions

ChetanAtGNU and others added 2 commits January 4, 2026 14:09

fix(AWS_BEDROCK_EXAMPLE.md): update api to bedrock

08948b1

CsBigDataHub force-pushed the feature/support-aws-bedrock-provider branch from d8a767c to 08948b1 Compare January 4, 2026 19:12

ericdallo added 2 commits January 5, 2026 15:07

Merge branch 'master' into feature/support-aws-bedrock-provider

6708ffb

Merge branch 'master' into feature/support-aws-bedrock-provider

b837bf0

ericdallo reviewed Jan 8, 2026

View reviewed changes

jumarko reviewed Jan 8, 2026

View reviewed changes

ChetanAtGNU added 4 commits January 16, 2026 21:23

fix(aws-bedrock): enhance tool result parsing and streaming support

1264202

aws-bedrock-tests:add test for parsing event stream with tool calls

7bd6868

Adds a new test case to verify parsing of event stream containing both text and tool call events, ensuring correct extraction of content and tool use details.

Merge branch 'upstream-master' into feature/support-aws-bedrock-provider

df97a44

ChetanAtGNU added 5 commits January 24, 2026 11:06

Merge branch 'upstream-master' into feature/support-aws-bedrock-provider

b367d7e

		This implementation uses Bearer token authentication, which requires
		an external proxy/gateway that handles AWS SigV4 signing.

Uh oh!

Add AWS Bedrock Converse/ConverseStream provider support #255

Are you sure you want to change the base?

Add AWS Bedrock Converse/ConverseStream provider support #255

Uh oh!

Conversation

CsBigDataHub commented Jan 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

CsBigDataHub commented Jan 4, 2026

Uh oh!

CsBigDataHub commented Jan 4, 2026

Uh oh!

ericdallo Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ericdallo commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

CsBigDataHub commented Jan 8, 2026

Uh oh!

jumarko Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

CsBigDataHub Jan 8, 2026

Choose a reason for hiding this comment

Uh oh!

jumarko Jan 9, 2026

Choose a reason for hiding this comment

Uh oh!

CsBigDataHub Jan 18, 2026

Choose a reason for hiding this comment

Uh oh!

CsBigDataHub commented Jan 18, 2026

Uh oh!

jumarko commented Jan 20, 2026

Uh oh!

CsBigDataHub commented Jan 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

CsBigDataHub commented Jan 4, 2026 •

edited

Loading

ericdallo Jan 8, 2026 •

edited

Loading

ericdallo commented Jan 8, 2026 •

edited

Loading

CsBigDataHub commented Jan 24, 2026 •

edited

Loading