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

Python: document region setup for Bedrock #9910

Open
eavanvalkenburg opened this issue Dec 9, 2024 · 3 comments
Open

Python: document region setup for Bedrock #9910

eavanvalkenburg opened this issue Dec 9, 2024 · 3 comments
Assignees
Labels
python Pull requests for the Python Semantic Kernel sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Comments

@eavanvalkenburg
Copy link
Member

No description provided.

@eavanvalkenburg eavanvalkenburg converted this from a draft issue Dec 9, 2024
@markwallace-microsoft markwallace-microsoft added python Pull requests for the Python Semantic Kernel triage labels Dec 9, 2024
@alliscode alliscode removed the triage label Dec 9, 2024
@alliscode
Copy link
Member

@eavanvalkenburg is this issue for yourself? I've assigned to you for now.

@TaoChenOSU
Copy link
Contributor

We already have a README on how to set up the bedrock service, including region. Please provide more details on this task @eavanvalkenburg, thanks!

@eavanvalkenburg
Copy link
Member Author

The reason I created this issue is because I got an error that Region wasn't set, but then when I look at the init signature of the Bedrock Chat Completion there is no way to set the region, so either we add a note on that in the init or a link to the Readme in there, and I think it also helps to write out the region setup directly in the readme, rather then just having a link, I do see that region_name is a supported arg in the underlying client, so adding Kwargs to BedrockChatCompletion with a pointer to the boto client would also help, as well as adding region to the settings of Bedrock, since it doesn't work without it and it is often something that should be driven by environment settings.

@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
python Pull requests for the Python Semantic Kernel sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Projects
Status: No status
Development

No branches or pull requests

5 participants