[Feature]: Support for Amazon Bedrock credentials (instead of Claude.ai account)

[valorisa]

Hello,

I would like jbsays to support authentication via Amazon Bedrock credentials (e.g. AWS access key / secret key / session token, or IAM role + region) instead of requiring a Claude.ai / Claude Code account.

Context:

• Today, jbsays initializes and stores credentials in .claude.json via the official Claude Code client, which expects a Claude.ai account.
• With Amazon Bedrock, Claude models can be accessed via the Bedrock API using standard AWS credentials, without a direct Claude.ai account, which is useful for enterprise or CI/CD setups.

Proposed changes:

• Add optional flags such as:
  • --bedrock / --use-bedrock
  • --aws-region (e.g. us-east-1)
  • Optionally: --aws-access-key-id, --aws-secret-access-key, --aws-session-token (or respect standard AWS credentials from ~/.aws/credentials / env vars).
• When --bedrock is set:
  • Do not run the Claude Code initialization flow and do not create .claude.json.
  • Instead, run a Bedrock‑aware wrapper inside the container that:
    • Uses the AWS SDK (e.g. SDK for Python/Node.js) to call bedrock-runtime with a Claude model.
    • Forwards the same prompt logic and project‑vision mechanism as the current implementation.
• Keep the default behavior (Claude.ai / Claude Code) unchanged for backward compatibility.

This would allow jbsays to be used in environments where:

• Only Bedrock access is allowed (no direct Claude.ai accounts).
• Access control is managed via IAM, VPC endpoints, or other AWS‑native mechanisms.

If the maintainers are open to this, I’m happy to help design the interface or contribute a PR that adds Bedrock support.

Thanks again.