θΏ™ζ˜―indexlocζδΎ›ηš„ζœεŠ‘οΌŒδΈθ¦θΎ“ε…₯任何密码
Skip to content

Conversation

@heiwais25
Copy link

Pull Request Type

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

Relevant Issues

Resolves #2864

What is in this change?

Support using AWS Credentials profile to avoid passing the static AWS Access Key and Secret Key manually.
It will also allow the easy integration with using IAM Role when the server is running on AWS EC2.

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated β†’ I'll work on this in separate PR since it can be larger change.
  • I have tested my code functionality
  • Docker build succeeds locally - Ran with each option (IAM, Session, and Profile)

Test Details

  1. Prepare AWS credentials by running aws configure
  2. Add the following configuration to the devcontainer.json.
{
  "mounts": [
    "source=${env:HOME}${env:USERPROFILE}/.aws,target=/root/.aws,type=bind"
  ],
  "remoteUser": "root",
}
  1. Run the server and check the Bedrock invocation with each option.

With the change,

  • IAM Selected
iam-credentials
  • Profile Selected
profile-credentials

@timothycarambat
Copy link
Member

closed by #2632

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]: Add support for AWS Credentials profile when connecting with Bedrock to avoid frequently updating temporary credentials

2 participants