Skip to content

Comments

Fix AWS LLM provider not recognized at startup#212

Merged
willingWill17 merged 4 commits intomainfrom
fix/aws-bedrock-not-initialized
Aug 17, 2025
Merged

Fix AWS LLM provider not recognized at startup#212
willingWill17 merged 4 commits intomainfrom
fix/aws-bedrock-not-initialized

Conversation

@willingWill17
Copy link
Collaborator

PR Description

This pull request resolves #206

Example Configuration

provider: aws
model: us.anthropic.claude-3-5-sonnet-20241022-v2:0  # Or another Bedrock-supported model
maxIterations: 50
aws:
  region: $AWS_REGION
  accessKeyId: $AWS_ACCESS_KEY_ID
  secretAccessKey: $AWS_SECRET_ACCESS_KEY
  sessionToken: $AWS_SESSION_TOKEN   # Optional, for temporary credentials

Notes

  • sessionToken is optional and can be used for temporary AWS credentials.
  • This change ensures better flexibility when integrating with AWS Bedrock.

@willingWill17 willingWill17 merged commit 6829869 into main Aug 17, 2025
5 checks passed
@willingWill17 willingWill17 deleted the fix/aws-bedrock-not-initialized branch September 6, 2025 09:03
Ptah-CT pushed a commit to DerAuctor/ct-cipher that referenced this pull request Oct 2, 2025
…-initialized

 Fix AWS LLM provider not recognized at startup
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.

1 participant