Merge pull request #19 from abap-ai/3-aws-bedrock-support

AWS Bedrock support

Author: wommel0

.github/workflows/downport.yml

@@ -41,6 +41,8 @@ jobs:
 
     - name: Check outputs
       if: ${{ steps.cpr.outputs.pull-request-number }}
+      env:
+        GH_TOKEN: ${{ secrets.PAT }}
       run: |
         echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}"
         echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}"

README.md

@@ -26,6 +26,7 @@ Currently supported providers:
 - Google Vertex AI
 - Deepseek (structured output currently not supported)
 - Google Gemini API
+- AWS Bedrock via Converse API Endpoint
 
 ## Features
 
@@ -87,10 +88,7 @@ In general for most parts interfaces are available to easily use custom implemen
 With the Beta release my focus is on using this library for further AI based topics (stay tuned) --> bug fixes have priority. Open a discussion or an issue if you have a specific requirement.
 Further features mid-term (check discord for short term plans and to discuss the current state):
 
-- More providers:
-  - AWS Bedrock
 - Workaround to force use required tool to simulate structured output where providers miss this feature (e.g. Azure AI Foundry)
-- Better UX for the settings and customizing tasks
 - Better error- and edge-case handling
 - Optional auto-retry for expected error cases (e.g. 429 HTTP Error)
 - Optimizations:

docs/ClientConfiguration.md

@@ -21,6 +21,10 @@ The table has the following fields which can be maintained as customzing:
 For models the internal model name must follow the format: /{location}/publishers/{publisher}/models/{modelid}
 Example: /europe-west3/publishers/google/models/gemini-1.5-flash
 
+### AWS Bedrock
+
+Make sure to use proper model names, especially taking [cross-region](https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-support.html) inference profiles into account. Note that tool use currently seems flaky with differnt models using the converse API in a different way.
+
 ## Recommendations
 
 Your feedback and experience is highly appreciated to extend this list:

docs/Provider.md

@@ -165,3 +165,20 @@ Provider configuration via Transaction ZLLM_PROVIDER_CONFIG:
 - RFC Desitination: created above
 - Auth Type: A (API Key)
 - Auth Value: Paste the API Key
+
+## [AWS Bedrock](https://aws.amazon.com/bedrock)
+
+Create the SM59 destination type "G" with:
+
+- HOST - use the endpoint as per [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/bedrock.html), e.g. bedrock.us-east-1.amazonaws.com
+- Port 443
+- Path Prefix /model
+- SSL Active & SSL Certificate as the usual SSL Client that has the required certificates (by default use the DFAUL SSL Client)
+- Special Options HTTP 1.1
+
+Provider configuration via Transaction ZLLM_PROVIDER_CONFIG:
+
+- Implementation Class: ZCL_LLM_CLIENT_AWS
+- RFC Desitination: created above
+- Auth Type: A (API Key)
+- Auth Value: {AWS Credential},{host from above},{region} for example credentialxyz,secret345345asdfsa,bedrock.us-east-1.amazonaws.com,us-east-1

src/aws/package.devc.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="utf-8"?>
+<abapGit version="v1.0.0" serializer="LCL_OBJECT_DEVC" serializer_version="v1.0.0">
+ <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
+  <asx:values>
+   <DEVC>
+    <CTEXT>AWS Bedrock Client</CTEXT>
+   </DEVC>
+  </asx:values>
+ </asx:abap>
+</abapGit>