I Tried Out Claude Opus 5.5, Now Available on Amazon Bedrock

Introduction

On September 22, 2026, Anthropic announced Claude Opus 5.5, and it became available on Amazon Bedrock the same day.

https://www.anthropic.com/news/claude-opus-5-5

I'll share the results of trying Opus 5.5 from the Tokyo region using Bedrock Runtime via an Inference Profile. The following was verified as of September 23, 2026, with AWS CLI 2.36.7.

Model Availability

I ran list-foundation-models in ap-northeast-1 and checked the Opus 5.5 entry.

{
  "modelId": "anthropic.claude-opus-5-5",
  "modelName": "Claude Opus 5.5",
  "providerName": "Anthropic",
  "inferenceTypesSupported": ["INFERENCE_PROFILE"],
  "modelLifecycle": {
    "status": "ACTIVE",
    "startOfLifeTime": "2026-09-22T10:00:00+00:00"
  }
}

The following two Opus 5.5 profiles were visible via list-inference-profiles from ap-northeast-1.

Invocation with the Converse API

This is a minimal invocation specifying the JP profile. Except for passing the profile ID to --model-id, the Converse API is written the same way as for other Claude models.

aws bedrock-runtime converse \
  --region ap-northeast-1 \
  --model-id jp.anthropic.claude-opus-5-5 \
  --messages '[{"role":"user","content":[{"text":"自己紹介を1文で"}]}]'

Here is the returned usage.

{
  "usage": {
    "inputTokens": 17,
    "outputTokens": 101,
    "totalTokens": 118,
    "cacheReadInputTokens": 0,
    "cacheWriteInputTokens": 0
  }
}

A response was also returned when I swapped --model-id to global.anthropic.claude-opus-5-5. Here is the usage when calling with the Global profile.

{
  "usage": {
    "inputTokens": 17,
    "outputTokens": 97,
    "totalTokens": 114,
    "cacheReadInputTokens": 0,
    "cacheWriteInputTokens": 0
  }
}

The Global profile may route to regions around the world, so if you have a requirement to keep data within Japan, use the JP profile.

Behavior by effort level

Effort is not a standard parameter of the Converse API; it is passed as a model-specific field in additionalModelRequestFields. The valid values of output_config.effort (per the Anthropic documentation) are five levels: low / medium / high / xhigh / max, with the default being medium.

https://docs.anthropic.com/en/api/messages

aws bedrock-runtime converse \
  --region ap-northeast-1 \
  --model-id jp.anthropic.claude-opus-5-5 \
  --messages '[{"role":"user","content":[{"text":"Pythonで素数判定する関数を書いて"}]}]' \
  --additional-model-request-fields '{"output_config":{"effort":"low"}}'

This time I measured three levels with the same prompt. Each value is a single measurement. Whether xhigh / max are accepted by Bedrock is unconfirmed.

With medium and high, a block with an empty reasoningText.text and a signature was returned. If you've written post-processing that assumes the presence of a reasoningContent block, choosing low means that block is not included, so you'll need a branch on the parsing side.

Fast mode support status

Anthropic's Fast mode is specified with service_tier: "fast". On the other hand, Bedrock's service_tier accepts four values: reserved / priority / default / flex. When I actually passed fast, a ValidationException occurred. At least within the scope I tried this time, Fast mode appears to be unavailable.

In addition, the Bedrock model card for Opus 5.5 also states that the only supported service tier is Standard.

https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-opus-5-5.html

Pricing

These are the listed values for Asia Pacific (Tokyo) on the Bedrock pricing page. The JP profile falls under Geo / In-region, and all items are 10% higher than Global Cross-region.

(All units are $/MTok)

The Global values are the same as Anthropic's official API pricing. Comparing Geo to Geo with Opus 5, Input / Output are down 20% from $5.50 / $27.50.

https://www.anthropic.com/pricing

https://aws.amazon.com/bedrock/pricing/

Summary

Claude Opus 5.5 became available on Bedrock on the same day as Anthropic's official announcement. Pricing is also 20% cheaper for Input / Output than Opus 5.

Among the Opus models usable with the JP profile, Opus 5 was never offered, so Opus 4.8 (jp.anthropic.claude-opus-4-8) was the latest, but now Opus 5.5 (jp.anthropic.claude-opus-5-5) can be selected. The AWS documentation also explicitly states "Keeps data within Japan regions". For Japanese workloads with data residency requirements, it is a candidate to switch to as is.

If you have no requirement to keep data within Japan, try Opus 5.5 with the Global profile, which is 10% cheaper; if you do, use the JP profile.

https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-opus-5-5.html