Skip to content

Add AWS Bedrock Provider #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jdegoes opened this issue Apr 30, 2025 · 13 comments · May be fixed by #9
Open

Add AWS Bedrock Provider #2

jdegoes opened this issue Apr 30, 2025 · 13 comments · May be fixed by #9

Comments

@jdegoes
Copy link

jdegoes commented Apr 30, 2025

No description provided.

@jdegoes
Copy link
Author

jdegoes commented Apr 30, 2025

/bounty $750

Copy link

algora-pbc bot commented Apr 30, 2025

💎 $750 bounty • Golem Cloud

Steps to solve:

  1. Start working: Comment /attempt #2 with your implementation plan
  2. Submit work: Create a pull request including /claim #2 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

❗ Important guidelines:

  • To claim a bounty, you need to provide a short demo video of your changes in your pull request
  • If anything is unclear, ask for clarification before starting as this will help avoid potential rework
  • Low quality AI PRs will not receive review and will be closed
  • Do not ask to be assigned unless you've contributed before

Thank you for contributing to golemcloud/golem-llm!

Attempt Started (UTC) Solution Actions
🟢 @Abiji-2020 May 01, 2025, 04:10:53 AM WIP
🟢 @vishalpatil1899 May 01, 2025, 05:24:20 AM WIP
🟢 @harsh-791 May 01, 2025, 06:40:31 AM #4 Reward
🟢 @Tsu-kimi May 01, 2025, 07:08:38 AM WIP
🟢 @Satyam12singh May 01, 2025, 09:02:03 AM WIP
🟢 @iambenkay May 01, 2025, 01:18:38 PM WIP
🟢 @onyedikachi-david May 09, 2025, 12:40:02 PM #9 Reward
🟢 @35C4n0r May 12, 2025, 02:30:12 AM WIP

@Tsu-kimi
Copy link

what should the short demo video include? Is it just a recording of the changes?

@Abiji-2020
Copy link

/attempt #2 I am new to it and will try my best on implementing. I have understood the current working of the llms here and We need to have a similar type for the aws bedrock too right ??

@vigoo
Copy link
Collaborator

vigoo commented May 1, 2025

In the video you can explain the changes and show that it works running all the (currently 6) test cases of the test:llm golem app using golem.

The PR should add a new module similar to the existing ones, and ideally should not touch the existing code at all.

@vishalpatil1899
Copy link

/attempt #2

1 similar comment
@harsh-791
Copy link

/attempt #2

@Tsu-kimi
Copy link

Tsu-kimi commented May 1, 2025

/attempt #2

@Satyam12singh
Copy link

/attempt #2
new to this but try my best.

@iambenkay
Copy link

/attempt #2

@Tsu-kimi
Copy link

Tsu-kimi commented May 2, 2025

@vigoo
Subject: Need Help Running Golem LLM Tests Locally on WSL – Dependency/Worker Issue

Goodday,

I'm currently trying to run the tests in the golem-llm-main repo on my local machine using WSL (Windows Subsystem for Linux) and I'm hitting a wall with worker/dependency issues. Here’s my setup:

Golem v1.2.1

Installed golem-x86_64-unknown-linux-gnu

Running inside WSL on Windows

Installed all required dependencies:

Rust

cargo-component v0.20

wac

Target wasm32-wasip1

my server is up and running to through

golem server run

I was able to deploy test:helper successfully with:

cd test/components-rust/test-helper golem component deploy test:helper --local

Then I tried deploying test:llm with:

cd ../test-llm golem component deploy test:llm --build-profile bedrock-debug --local
Both components seem to deploy without error, showing outputs like:
Updated component test:helper to version 7 ╔═ ║ Component name: test:helper ║ Component ID: a38705ec-c991-4d8b-b14f-bacc125538a3 ║ Component type: Durable ║ Component version: 7 ║ Component size: 2.85 MiB ║ Created at: 2025-05-02 07:33:49.044491500 UTC ║ Exports: test:helper-exports/test-helper-api.{inc-and-get}() -> u64 ╚═

Updated component test:llm to version 9 ╔═ ║ Component name: test:llm ║ Component ID: eb631793-6062-49f3-9293-252a236385c4 ║ Component type: Durable ║ Component version: 9 ║ Component size: 52.96 MiB ║ Created at: 2025-05-02 07:34:14.393445500 UTC ║ Exports: ║ test:llm-exports/test-llm-api.{test1}() -> string ║ test:llm-exports/test-llm-api.{test2}() -> string ║ test:llm-exports/test-llm-api.{test3}() -> string ║ test:llm-exports/test-llm-api.{test4}() -> string ║ test:llm-exports/test-llm-api.{test5}() ║ test:llm-exports/test-llm-api.{test6}() -> string ║ Dynamic WASM RPC links: ║ test:helper-client/test-helper-client: ║ test-helper-api: test:helper-exports/test-helper-api ╚═

However, when I attempt to create a worker, I encounter the following error:

Worker Service - Error: 500 Internal Server Error, Failed to create worker eb631793-6062-49f3-9293-252a236385c4/ test:llm: Failed to pre-instantiate worker -1/eb631793-6062-49f3-9293-252a236385c4/test:llm: component imports instance golem:durability/durability@1.2.0, but a matching implementation was not found in the linker.
I've tried invoking the worker for several tests, such as test1, test2, test3, and so on, but the same error occurs for all.

This issue seems to be related to the golem:durability/durability@1.2.0 component missing in the linker. I don't know if i skipped a step during my installation but Any guidance or suggestions would be much appreciated!

Thanks in advance.

@Abiji-2020
Copy link

@Tsu-kimi you need to use the dev release instead of the stable one. More details on #3

@35C4n0r
Copy link

35C4n0r commented May 12, 2025

/attempt #2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants