Allow for authentication via bedrock instead of Anthropic directly

[knechtionscoding]

We would like to use Kelos but would like it to call models directly via bedrock rather than via the anthropic API. Seeing as it is running the claude-sdk which should support this out of the box, we believe that allowing this as a authentication model is worthwhile

[kelos-bot]

🤖 Kelos Task Status

Task kelos-triage-780 has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/feature
Priority: priority/important-longterm — Valuable for AWS-centric users but not blocking core functionality; a partial workaround exists via podOverrides.env
Actor: needs human — Requires API design decisions on how to model Bedrock credentials (new credential type, AWS credential fields, etc.)

Status: STILL VALID

Evidence:

• The codebase currently supports only two credential types: api-key and oauth (api/v1alpha1/task_types.go:11-16)
• The controller injects ANTHROPIC_API_KEY for claude-code agents (internal/controller/job_builder.go:148), with no support for AWS/Bedrock-specific env vars (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, CLAUDE_CODE_USE_BEDROCK, etc.)
• No references to "bedrock", "vertex", or AWS env vars exist anywhere in the codebase
• Claude Code CLI does support Bedrock natively via environment variables, so the underlying tool is capable — Kelos just doesn't expose the configuration path
• Partial workaround: Users can inject arbitrary env vars via podOverrides.env (added in task_types.go:63-67), but built-in credential env vars take precedence, making it awkward — a dummy ANTHROPIC_API_KEY secret would still be required

Duplicates found: None found

Recommendation: KEEP OPEN — This is a legitimate feature gap. Implementation likely involves: (1) adding a new credential type (e.g., bedrock) or extending the existing secret-based flow to support AWS credential keys, (2) updating job_builder.go to inject the correct AWS env vars when Bedrock is selected, and (3) updating docs/examples. A human maintainer should decide on the API design before implementation begins.

[gjkim42]

/kelos plan