Add AWS credential provider support for Bedrock#454
Add AWS credential provider support for Bedrock#454jscheid wants to merge 1 commit intocrmne:mainfrom
Conversation
Allows passing Aws::CredentialProvider objects (instance profile, assume role, etc.) instead of static credentials. Provider takes precedence when both are configured.
|
@tpaulshippy here's a PR as discussed, please let me know what you think? |
|
Looks great! Much nicer than the approach I'm using. |
|
Great... Looking forward how this PR progress. |
|
We have big need for this now. Thank you ! |
|
For apps running in aws this feature enables best practice for service to service auth. We shouldnt need to create new iam users and manage creds. Please prioritize this PR! |
FYI - this is achievable now. See #16 (comment) - this PR just makes it easier. |
Thank you 🙏 |
Is there any estimate on release of this feature? in the meantime, I'm looking into implementing the solution from the gist shared by @tpaulshippy (or the derived gist from a commenter in that thread, not sure which approach to prefer yet) to get Bedrock to work with my IAM policy setup in production |
What this does
Allows passing
Aws::CredentialProviderobjects (instance profile, assume role, etc.) instead of static credentials. Provider takes precedence when both are configured. This is a solution to the problem of authenticating with e.g. role-based permissions, as discussed here.Type of change
Scope check
Quality check
overcommit --installand all hooks passbundle exec rake vcr:record[provider_name]bundle exec rspecmodels.json,aliases.json)API changes
Related issues
Related to #16