CLAUDE-CODE PUB_DATE: 2026.04.30

CLAUDE CODE 2.1.122/123: BEDROCK SERVICE TIERS + CLEANER TELEMETRY

Claude Code now lets you choose Amazon Bedrock service tiers and fixes telemetry and cloud integration bugs. The latest releases add an ANTHROPIC_BEDROCK_SERVI...

Claude Code now lets you choose Amazon Bedrock service tiers and fixes telemetry and cloud integration bugs.

The latest releases add an ANTHROPIC_BEDROCK_SERVICE_TIER env var that sets the X-Amzn-Bedrock-Service-Tier header, giving you explicit control over default, flex, or priority tiers for Amazon-hosted Claude calls (releases, summary).

OpenTelemetry attributes for api_request/api_error are now properly typed as numbers, with a new claude_code.at_mention event. There are also targeted fixes for Vertex AI/Bedrock structured-output errors, proxy count_tokens failures, and an OAuth 401 loop when betas are disabled releases.

If you’re exploring “lightweight agents,” Routines are getting real use in production-style recurring tasks, without running your own stack guide.

[ WHY_IT_MATTERS ]
01.

You can now tune Claude-on-Bedrock calls for latency or throughput without code changes, which helps SLOs and cost control.

02.

Telemetry types are corrected, reducing parsing errors and making OTel dashboards more reliable.

[ WHAT_TO_TEST ]
  • terminal

    Benchmark default vs flex vs priority tiers via ANTHROPIC_BEDROCK_SERVICE_TIER; capture p95 latency, throttling, and any error-rate shifts.

  • terminal

    Validate OTel pipelines: ensure numeric attributes ingest as numbers, and surface the new claude_code.at_mention event in dashboards.

[ BROWNFIELD_PERSPECTIVE ]

Legacy codebase integration strategies...

  • 01.

    Allowlist and forward X-Amzn-Bedrock-Service-Tier through proxies/gateways; verify egress policies don’t strip it.

  • 02.

    If you cast OTel attributes from strings, remove workarounds and update schemas; retest Vertex AI/Bedrock structured-output paths and proxy count_tokens.

[ GREENFIELD_PERSPECTIVE ]

Fresh architecture paradigms...

  • 01.

    Parameterize service tier by environment or task class (e.g., priority for interactive PRs, flex for batch jobs).

  • 02.

    Adopt OTel from day one with numeric attribute types; add alerts on api_error rates and track at_mention resolution.

Enjoying_this_story?

Get daily CLAUDE-CODE + SDLC updates.

  • Practical tactics you can ship tomorrow
  • Tooling, workflows, and architecture notes
  • One short email each weekday

FREE_FOREVER. TERMINATE_ANYTIME. View an example issue.

GET_DAILY_EMAIL
AI + SDLC // 5 MIN DAILY