---
title: Claude Opus 5.5 on AWS (September 2026): Bedrock Adoption Guide
description: On September 22, 2026 AWS shipped Claude Opus 5.5 — 1M-token context, thinking always on, ZDR by default on Bedrock. Anthropic lists $4/$20 per million tokens. Here is the routing call and what breaks from Opus 5.
url: https://www.factualminds.com/blog/claude-opus-5-5-aws-bedrock-2026/
datePublished: 2026-09-23T00:00:00.000Z
dateModified: 2026-09-23T00:00:00.000Z
author: palaniappan-p
category: AI Agents
tags: amazon-bedrock, claude, anthropic, ai-agents, aws-ai, foundation-models
---

# Claude Opus 5.5 on AWS (September 2026): Bedrock Adoption Guide

> On September 22, 2026 AWS shipped Claude Opus 5.5 — 1M-token context, thinking always on, ZDR by default on Bedrock. Anthropic lists $4/$20 per million tokens. Here is the routing call and what breaks from Opus 5.

> **AWS lifecycle notice (June 30, 2026)** — Amazon Bedrock Agents Classic is in maintenance for new customers after **July 30, 2026**. Net-new agent builds should use [Bedrock AgentCore](/blog/amazon-bedrock-agentcore-production/). Full matrix: [lifecycle roundup](/blog/aws-service-lifecycle-updates-june-2026/).

On **September 22, 2026**, AWS [announced Claude Opus 5.5 on AWS](https://aws.amazon.com/about-aws/whats-new/2026/09/claude-opus-5-5-aws/) — the first Claude 5.5 model, and Anthropic’s most capable Opus. Bedrock is the path with **zero data retention (ZDR) by default**, regional residency, and Guardrails / Knowledge Bases composition. Claude Platform on AWS is the Anthropic-native console with AWS billing and auth.

If you already run [Claude Opus 5](/blog/claude-opus-5-aws-bedrock-2026/) (GA July 24, 2026), treat this as a **lane promotion**, not a global model-ID swap. The [Bedrock model card](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-opus-5-5.html) pins the architecture: **1M-token context**, **128K max output**, adaptive thinking **always on**. Anthropic’s [model overview](https://platform.claude.com/docs/en/models/opus-5-5/overview) adds the price and the breaking changes. This post is the adoption lens.

---

## What changed on September 22, 2026

Per AWS, Opus 5.5 is the enterprise Opus workhorse: long-running coding and knowledge work, with a report-back style that says what it did, what it found, and what it needs next. Anthropic says it completes tasks with **fewer tokens than Opus 5**, at a **lower price per token**, and with **cheaper cache reads**.

| Path                       | ZDR               | Best when                                                                                     |
| -------------------------- | ----------------- | --------------------------------------------------------------------------------------------- |
| **Amazon Bedrock**         | **On by default** | AWS-native governance, regional residency, Guardrails / Knowledge Bases on `bedrock-runtime` |
| **Claude Platform on AWS** | Confirm in console | Teams that want Anthropic-native APIs and console UX with AWS billing                        |

EOL is no sooner than **September 22, 2027**, with a 6-month legacy period, per the model card.

---

## Specs that change architecture

From the [Claude Opus 5.5 model card](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-opus-5-5.html) unless noted:

| Spec             | Value                                                                 | Why it matters                                                                                          |
| ---------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Context window   | **1M tokens**                                                         | Same ceiling as Opus 5 — you still pay for what you send                                                |
| Max output       | **128K tokens**                                                       | Long artifacts; watch client and stream timeouts                                                        |
| Reasoning        | **Adaptive thinking, always on**                                      | Cannot be disabled. Effort: low, medium, high, xhigh, max. **Default: medium**                         |
| Knowledge cutoff | **June 2026**                                                         | One month newer than the Opus 5 card (May 2026)                                                         |
| Prompt cache     | **Min 512 tokens**, up to 4 checkpoints, 5-minute or 1-hour TTL       | Checkpoints accepted on `system`, `messages`, and `tools`                                              |
| Computer use     | `computer_20251124` on the Bedrock card                               | Anthropic says that tool string is rejected on the Claude API and Google Cloud — do not share one ID   |
| Compaction       | `compact-2026-09-04` on `bedrock-runtime`                             | Long jobs can compact; confirm the beta header before you depend on it                                 |
| Launch           | **September 22, 2026**                                                | Active. In-region on `bedrock-runtime` is **N/A** — use a geo or global profile                        |

**Guardrails, Knowledge Bases, Flows, and Agents are on `bedrock-runtime`, not on `bedrock-mantle`.** Mantle supports streaming, prompt caching, abuse detection, count tokens, and computer use. Structured outputs are unsupported on both endpoints, per the card.

**Opinionated take:** default **new** long-running coding and knowledge-work lanes to Opus 5.5 on **Bedrock** (`bedrock-runtime`, ZDR default, explicit `maxTokens`). Keep high-QPS chat on Sonnet 5, Haiku 4.5, or Nova. Leave Opus 5 in place until the frozen-prompt bakeoff says 5.5 wins on **cost per completed task**, not on the version number.

Trade-off you accept: fewer tokens and a lower published per-token price versus a handler rewrite, because thinking cannot be switched off and inter-tool progress text moves into thinking blocks.

---

## Prices: cite Anthropic, then confirm Bedrock

Anthropic’s overview (Bedrock listed as a platform) publishes:

| | Per 1M tokens |
| --- | --- |
| Input | **$4** |
| Output | **$20** |
| 5-minute cache write | **$5** |
| 1-hour cache write | **$8** |
| Cache read | **$0.20** |

The Bedrock model card does **not** repeat those dollars. It says Opus 5.5 is billed through **AWS Marketplace** (charges show under the provider, not under Amazon Bedrock) and points at the [Bedrock pricing page](https://aws.amazon.com/bedrock/pricing/). On September 23, 2026 that page’s static extract did not include an Opus 5.5 dollar row. **Do not re-forecast from the Anthropic list until the Bedrock sheet shows the rate.**

Our previously published Opus 5 Bedrock on-demand pin remains **$15 / $75** per million input/output tokens in the calculators. That row stays until the pricing page replaces it.

---

## Invoke Opus 5.5 (Converse, explicit maxTokens)

Context: boto3 Bedrock Runtime, `us-east-1`, global inference profile. The model card’s sample `converse()` call omits `maxTokens`. Leaving it unset reserves toward the **128K** ceiling and is a common `ThrottlingException` cause. Set it.

```python
import boto3

client = boto3.client('bedrock-runtime', region_name='us-east-1')

response = client.converse(
    modelId='global.anthropic.claude-opus-5-5',
    messages=[
        {
            'role': 'user',
            'content': [
                {
                    'text': 'Summarize the failure modes in this migration plan and propose a rollback checklist.'
                }
            ],
        }
    ],
    inferenceConfig={'maxTokens': 4096},
)

blocks = response['output']['message']['content']
print('\n'.join(b.get('text', '') for b in blocks if 'text' in b))
```

Profile IDs from the model card:

- Geo: `us.anthropic.claude-opus-5-5`, `eu.anthropic.claude-opus-5-5`, `au.anthropic.claude-opus-5-5`, `jp.anthropic.claude-opus-5-5`
- Global: `global.anthropic.claude-opus-5-5`
- Mantle Messages base ID: `anthropic.claude-opus-5-5` at `https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages`

US geo keeps data in US and Canada regions. EU, AU, and JP geos stay inside those geographies. Global has no residency constraint. Confirm the live regional matrix before you hardcode a profile — a static fetch of the card did not preserve the region checkmarks.

> **What broke (pattern, not a cited client)** — An Opus 5 wrapper that set thinking off, or that streamed text between tool calls as a progress UI, does not survive the move. Thinking cannot be disabled, and Anthropic says that inter-tool text arrives in thinking blocks whose text is empty at the default `display` setting. The progress UI goes quiet until the client requests a display value that returns the text. Forced tool choice returns an error instead of a tool call.

---

## Where Opus 5.5 fits

| Lane                                              | Prefer                                      | Why                                                                                          |
| ------------------------------------------------- | ------------------------------------------- | -------------------------------------------------------------------------------------------- |
| Long-running coding and knowledge work            | **Opus 5.5** on Bedrock                     | New Opus default after a bakeoff; ZDR on by default                                         |
| Opus 5 lanes that already meet quality and budget | **Stay on Opus 5**                          | Version number is not a promotion                                                           |
| Agentic coding with a cost cap                    | **Sonnet 5**                                | Mid-tier; validate before paying Opus rates                                                 |
| Multi-hour autonomous jobs under Covered Model    | **Fable 5.1** after legal sign-off          | Different retention contract — see the [Fable guide](/blog/claude-fable-5-aws-bedrock-mythos-class-guide-2026/) |
| High-QPS classification                           | **Haiku 4.5, Nova 2 Lite, or GPT-6 Luna**   | Opus 5.5 is the wrong default                                                               |

---

## Rollout: 2-week evaluation

1. **Pick three lanes** — multi-file coding, one job that runs at least 30 minutes, one document-heavy analysis.
2. **Freeze prompts** — replay production-representative traces. No ad-hoc demos.
3. **Score quality pass rate, latency to a completed task, and cost per completed task.** Token list price alone will lie if 5.5 spends fewer tokens, or if always-on thinking spends more.
4. **Rewrite the three breaking paths** — thinking-off flags, forced tool use, and inter-tool progress streaming — in a branch before the bakeoff, or the scores measure your client bugs.
5. **Promote lane-by-lane.** Block any pull request that flips the production default model ID before scores land.

Pair agent lanes with [AgentCore](/blog/amazon-bedrock-agentcore-production/) and [token budgets](/blog/aws-bedrock-cost-optimization-token-budgets-model-selection/).

---

## What to Do This Week

1. Open the [Opus 5.5 model card](https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-opus-5-5.html) and copy the geo or global profile that matches your residency rule.
2. Smoke-test Converse in a non-prod account with `maxTokens` set (start at 1024).
3. Grep callers for disabled thinking, forced tool choice, and progress text read from assistant text between tools.
4. Keep Guardrails on `bedrock-runtime`. Do not assume Mantle applies them.
5. Schedule the three-lane eval. Leave Opus 5 as the production pin until it finishes.

---

## What This Post Doesn't Cover

- A confirmed Bedrock dollar rate. Anthropic’s $4 / $20 list is cited above; the Bedrock price sheet did not show an Opus 5.5 row in the extract we checked on September 23, 2026.
- A first-party FactualMinds latency or cost benchmark of Opus 5.5 versus Opus 5. We have not run that bakeoff.
- Claude Platform on AWS console steps beyond the Bedrock-first recommendation.
- Full AgentCore packaging for overnight jobs.

Use this as the adoption frame, then validate on your prompt distribution and quota envelope.

---

## Related reading

- [Claude Opus 5 on AWS Bedrock (July 2026)](/blog/claude-opus-5-aws-bedrock-2026/)
- [Claude Sonnet 5 on AWS (June 2026)](/blog/claude-sonnet-5-aws-bedrock-2026/)
- [Claude Fable 5 on AWS: Mythos-Class Guide](/blog/claude-fable-5-aws-bedrock-mythos-class-guide-2026/)
- [GPT-6 Sol and Luna on Amazon Bedrock (September 2026)](/blog/openai-gpt-6-sol-luna-amazon-bedrock-2026/)
- [AWS Bedrock Cost Optimization: Token Budgets and Model Selection](/blog/aws-bedrock-cost-optimization-token-budgets-model-selection/)
- [Amazon Bedrock AgentCore: Production-Ready AI Agents](/blog/amazon-bedrock-agentcore-production/)

## FAQ

### Where can I access Claude Opus 5.5 on AWS?
AWS offers two paths: Amazon Bedrock and Claude Platform on AWS. Bedrock ships Opus 5.5 with zero data retention (ZDR) by default, regional data residency, and composition with Guardrails and Knowledge Bases on bedrock-runtime. Claude Platform on AWS gives Anthropic-native console and APIs with AWS billing and authentication.

### What is the Bedrock model ID for Claude Opus 5.5?
The AWS model card lists anthropic.claude-opus-5-5. On bedrock-runtime, in-region inference is not available — use a geo profile (us.anthropic.claude-opus-5-5, eu.anthropic.claude-opus-5-5, au.anthropic.claude-opus-5-5, or jp.anthropic.claude-opus-5-5) or global.anthropic.claude-opus-5-5. The Mantle Messages ID is the same base ID. Set maxTokens explicitly.

### Should we move every Opus 5 workload to Opus 5.5 immediately?
No. Opus 5.5 is the new Opus workhorse for long-running coding and knowledge work, and Anthropic says it uses fewer tokens than Opus 5 at a lower price per token. Thinking cannot be turned off, and forced tool use errors. Promote lane-by-lane after a frozen-prompt bakeoff on quality, latency, and cost per completed task.

### What are the published prices for Claude Opus 5.5?
Anthropic’s model overview lists $4 per million input tokens and $20 per million output tokens, with cache reads at $0.20, 5-minute cache writes at $5, and 1-hour cache writes at $8. The Bedrock model card does not embed a dollar table — it points at the Amazon Bedrock pricing page and notes Marketplace billing under the provider. Confirm that sheet before you re-forecast. Do not treat the Anthropic list as a confirmed Bedrock invoice rate.

### What breaks when code written for Opus 5 calls Opus 5.5?
The AWS model card says adaptive thinking is always on and cannot be disabled; effort defaults to medium (low, medium, high, xhigh, max). Anthropic also documents that forced tool use returns an error, thinking blocks are tied to the conversation, and text between tool calls comes back in thinking blocks that are empty at the default display setting. Handlers that assumed thinking could be switched off, or that streamed inter-tool text as progress, need a code change.

---

*Source: https://www.factualminds.com/blog/claude-opus-5-5-aws-bedrock-2026/*