docs: clarify Bedrock IAM role support - #350
Merged
Merged
Conversation
Refs kagent-dev#349 Signed-off-by: Maaz Ghani <maazghani@gmail.com>
Contributor
Author
|
Can I get a review? @christian-posta @craigbox @claude @dobesv |
dobesv
approved these changes
Apr 17, 2026
dobesv
left a comment
dobesv
left a comment
Contributor
There was a problem hiding this comment.
Looks good to me. Note however that I don't have the power to merge this ...
Contributor
Author
|
@dobesv who does? |
Contributor
|
What seems to work is to join the discord and ping the #prs channel there. I'm not sure how to get a list of all the maintainers |
peterj
approved these changes
Apr 23, 2026
Contributor
|
thanks for your contribution @maazghani ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #349
This MR improves the Amazon Bedrock docs for kagent by making the Kubernetes authentication story clearer. The current docs can be read as if IRSA/workload identity is not supported, which may lead users toward access keys and Kubernetes secrets as the primary setup. These changes clarify that IRSA is supported today and should generally be the preferred approach for Kubernetes deployments.
The update also explains that Bedrock uses the standard AWS credential chain, adds IAM role and ServiceAccount-based setup examples, and makes apiKeySecret guidance more precise by noting that it is optional and only needed when using static access keys.
cc @boriscosic