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

feat: support for iam roles for bedrock client #2632

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dannysteenman
Copy link

@dannysteenman dannysteenman commented Nov 14, 2024

Pull Request Type

  • ✨ feat
  • πŸ› fix
  • ♻️ refactor
  • πŸ’„ style
  • πŸ”¨ chore
  • πŸ“ docs

Relevant Issues

resolves #2588

What is in this change?

This feature includes the ability to authenticate with bedrock on aws using your iam role instead of using long term iam credentials. It should be backwards compatible with people who have setup:

AWS_BEDROCK_LLM_ACCESS_KEY_ID=
AWS_BEDROCK_LLM_ACCESS_KEY=

Additional Information

In the UI it looks like this now, default:

SCR-20241114-jaaq

when you enable the iam role:

SCR-20241114-jacj

Please verify it and let me know if you have some feedback, so I can improve it, then I can also update the docs once you're happy with the result.

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • [ x ] I have tested my code functionality
  • [ x] Docker build succeeds locally

@dannysteenman dannysteenman changed the title Master feat: support for iam roles for bedrock client Nov 14, 2024
@timothycarambat timothycarambat self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEAT]: AWS SDK Credential Provider Chain Not Following Standard Order in Bedrock Integration
2 participants