Skip to content
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

[BUG] - unable to run claude models in us-west-2 #286

Open
tnh opened this issue Apr 28, 2024 · 5 comments
Open

[BUG] - unable to run claude models in us-west-2 #286

tnh opened this issue Apr 28, 2024 · 5 comments
Labels
needs-info Need more information such as reproduction step stale Issue labeled as stale will be closed automatically

Comments

@tnh
Copy link

tnh commented Apr 28, 2024

Describe the bug

Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
A clear and concise description of what the bug is.

To Reproduce

  • setting AWS_DEFAULT_REGION=us-east-2
  • closing repo
  • running ./bin.sh

Then I was unable to access any model - and would see the following
Screenshot 2024-04-29 at 8 47 52 am

I have access to all the models in the us-east-2 region:

Screenshot 2024-04-29 at 8 46 09 am Screenshot 2024-04-29 at 8 46 59 am

the model id does seem like the same model id:

Screenshot 2024-04-29 at 8 47 32 am

I see the following two log messsages in the cloudwatch logs for the Websocket Lambda:

Screenshot 2024-04-29 at 8 45 16 am Screenshot 2024-04-29 at 8 44 59 am

This is the message in the browser on the client side of the WSS call:

"{\"conversationId\":\"01HWKDG43PGTFQNRP1Y9WK45TM\",\"message\":{\"content\":[{\"body\":\"test\",\"contentType\":\"text\"}],\"model\":\"claude-v3-opus\",\"role\":\"user\",\"feedback\":null,\"parentMessageId\":\"system\"},\"token\":\"eyJraWQiOiJzY2k0aWMxUXZEVTEwU2lUM2gyRnNUZ1dBTVM5ZlNsVFErK0g3cUlcL21GND0iLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiI3OGIxMjNmMC1lMDkxLTcwNTAtZTIxOC01OWRhNTMzZWFhZmUiLCJjb2duaXRvOmdyb3VwcyI6WyJBZG1pbiIsIlB1Ymxpc2hBbGxvd2VkIl0sImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJpc3MiOiJodHRwczpcL1wvY29nbml0by1pZHAudXMtd2VzdC0yLmFtYXpvbmF3cy5jb21cL3VzLXdlc3QtMl9DbzcxbUpzSXAiLCJjb2duaXRvOnVzZXJuYW1lIjoiNzhiMTIzZjAtZTA5MS03MDUwLWUyMTgtNTlkYTUzM2VhYWZlIiwib3JpZ2luX2p0aSI6ImYwNGM2ZmYwLTY5YTItNGQxOC1hMDdmLTIwYmQ2MjlkYTExNyIsImF1ZCI6IjZwaDZ0Z3RrZjQ1a3I5Mm0xOG85dHNxbGwiLCJldmVudF9pZCI6ImUzOGVjNDZkLWE5MTUtNDA5YS04YmRkLTZiNTViNjc4ODQ1YyIsInRva2VuX3VzZSI6ImlkIiwiYXV0aF90aW1lIjoxNzE0MjA0MzEwLCJleHAiOjE3MTQ0MjkzODQsImlhdCI6MTcxNDM0Mjk4NCwianRpIjoiMDQzOWI3NGEtNDEyMS00ZWZjLThhY2YtZTk4ZmM1MTljNGY2IiwiZW1haWwiOiJ0aG9ybmlicm9va0BzZWVrLmNvbS5hdSJ9.BPwjF8w8M0PAAnZa-wg0SVAaXWM1RcPuznv4gbzy6AA-OAoFb14X-i27vYiKaLdkzRzBAb2KTCIs1h50BBirz5bbR41q_cikjBw5tpReaj78XyvVhwvDVWd7DiwjwbPYx_vWw-qTiC8vmKXvTWDRq86WYduJO9ny6oyyHUqbkaIeNJqT2VQ7Yitflw___FoTQIaqvH27hj17HJjUCXuLn_MljeEHgUaYP7x7tbfisQt5DGxa35PQ66fvvSHlirDlHOGtWFw2DdbG07L1l0XcfDZAVlM9_PYv0ppiuNpUGXT6Q5t0axx4Jc354OBUWKgNS5txyELOAfRr2HH_MTZwdw\"}"

Additional context

Add any other context about the problem here.

@statefb
Copy link
Contributor

statefb commented May 2, 2024

Could you please let me know Sonnet / Haiku are available?

@statefb statefb added the needs-info Need more information such as reproduction step label May 7, 2024
@prometheusresearchlabs-partha

Hello, I have the exact same error as tnh, and to confirm, I also have Haiku and Sonnet enabled, these are working fine in the Chat, Opus is not and is showing the same error as above, if you require any further context, please let me know

@statefb
Copy link
Contributor

statefb commented May 18, 2024

Have both of you modified bedrockRegion to us-west-2?
ref: https://github.com/aws-samples/bedrock-claude-chat#deploy-using-cdk

@prometheusresearchlabs-partha

Yes, Claude 3 Opus is only available in Oregon hence bedrockRegion is set to us-west-2 in cdk.json, I also tried again and replaced any instance of us-east-1 to us-west-2 and still have this error. Also tried in multiple AWS accounts just in case

Copy link

github-actions bot commented Jun 2, 2024

This issue has been labeled as "stale" due to no response by the reporter within 1 month (and 14 days after last commented by someone). And it will be closed automatically 14 days later if not responded.

@github-actions github-actions bot added the stale Issue labeled as stale will be closed automatically label Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-info Need more information such as reproduction step stale Issue labeled as stale will be closed automatically
Projects
None yet
Development

No branches or pull requests

3 participants