Feature Request: Support AWS Bedrock as Alternative Path for Claude Models
Background
Currently, baz-cli supports using Anthropic Claude models via direct Anthropic API key (ANTHROPIC_TOKEN). For teams and enterprises using AWS Bedrock to access Claude models, alternative authentication methods would be valuable.
Suggested Improvements:
It would be helpful if Baz CLI could support:
- AWS Standard SDK Authentication
- Allow using native AWS credential chain (env variables, ~/.aws/credentials setup, IAM roles, etc) so that users can authenticate as they would with any other AWS SDK tool.
- Bedrock API Token Authentication
- Allow passing a Bedrock API token (if/when such a method is available, for environments where static tokens are preferred).
Supporting both lets users pick the workflow suited to their environment (dev machines, CI, EC2, or managed roles).
Questions for the Baz Team
- Is there a specific Claude model the CLI currently expects or defaults to when using Anthropic?
- If adding Bedrock support, should the model ID be configurable or be locked to a known compatible version?
Thank you for considering this feature!
Feature Request: Support AWS Bedrock as Alternative Path for Claude Models
Background
Currently, baz-cli supports using Anthropic Claude models via direct Anthropic API key (
ANTHROPIC_TOKEN). For teams and enterprises using AWS Bedrock to access Claude models, alternative authentication methods would be valuable.Suggested Improvements:
It would be helpful if Baz CLI could support:
Supporting both lets users pick the workflow suited to their environment (dev machines, CI, EC2, or managed roles).
Questions for the Baz Team
Thank you for considering this feature!