Balinder Walia
Claude Opus 5 is live on Amazon Bedrock and Claude Platform on AWS. Here is the Workstation take — what it means for developers and business teams, when to use it, and how to start. Deep dive with code in the long article.
In one paragraph. Opus 5 is Anthropic’s strongest Opus-tier model on AWS (launched 24 Jul 2026): better agentic coding, long-running agents, and document-heavy knowledge work, with a 1M-token context window. On Amazon Bedrock you get zero data retention (ZDR) by default, Guardrails, and AWS IAM/billing. Use it for hard engineering and agent fleets; keep Sonnet/Haiku for volume. Full router advice: Claude model comparison.
Adapted for Workstation readers from the AWS Machine Learning Blog announcement — Introducing Claude Opus 5 on AWS.
Why business teams should care
- Production agents that run longer — multi-hour / overnight workflows with better recovery from errors.
- Codebase-scale engineering — navigate large repos, ship higher-quality patches, fewer hand-holding loops.
- Enterprise document work — deeper reasoning over long policies, contracts, and financial packs.
- Governance on Bedrock — ZDR by default, regional residency options, no “shadow SaaS” for sensitive corpora.
Why developers should care
- Model IDs on Bedrock:
global.anthropic.claude-opus-5(and geo variantsus./eu./au.). - Call via Invoke, Converse, or Anthropic Messages on bedrock-mantle.
- Adaptive reasoning on by default; prompt caching (5m / 1h); mid-conversation tool add/remove.
- Opus-tier economics with Fable-class intelligence claimed in many domains — reserve Fable/Mythos for peak-critical paths.
Two doors on AWS
| Path | Best when |
|---|---|
| Amazon Bedrock | ZDR default, Guardrails, Knowledge Bases, AgentCore, AWS-native security |
| Claude Platform on AWS | Anthropic-native console/APIs with AWS auth + billing; ZDR on request |
Quick start (Bedrock Converse)
import boto3
client = boto3.client("bedrock-runtime", region_name="us-east-1")
resp = client.converse(
modelId="global.anthropic.claude-opus-5",
messages=[{"role": "user", "content": [{"text": "Refactor this service for multi-region failover."}]}],
inferenceConfig={"maxTokens": 4096},
)
print(resp["output"]["message"]["content"])
Workstation recommendation
Pair Opus 5 on Bedrock with your existing agent stack (Review Bots, multi-agent crews, GitOps gates). Use Opus 5 for planner/lead-engineer agents; route routine tickets to cheaper models. See the long article for Invoke vs Mantle, geo IDs, caching, and a production checklist. Published by Workstation.