Skip to main content

Supported models

For the administrator filling in Sonnet model id (runner) and Opus model id (planner) in the deployment wizard, and the engineer enabling model access in the target AWS account: Studio runs on Amazon Bedrock models in your AWS account, and each Studio version supports a fixed set: a runner model that agents and workers use, a planner model that coordinates and governs, a fixed embeddings model for knowledge graphs, and a redactor for personally identifiable information (PII), which is the planner. Before you start, know the deployment's region (it decides the inference zone, us or eu) and have access to the Amazon Bedrock console in the target account with permission to manage model access.

Models for Studio 2.0.14​

This table is per Studio version. It describes Studio 2.0.14 deployed from Organisations 1.0.16; a later version publishes its own table. Studio 2.0.14 runs Claude 4.x models only: Claude Sonnet 4.6 as the runner, Claude Opus 4.6, 4.7 or 4.8 as the planner, and the embeddings model is fixed.

RoleModelBedrock model id (as offered in the wizard)Choice in the wizardDefault
RunnerClaude Sonnet 4.6anthropic.claude-sonnet-4-6The only optionYes
PlannerClaude Opus 4.6anthropic.claude-opus-4-6-v1One of threeYes
PlannerClaude Opus 4.7anthropic.claude-opus-4-7One of threeNo
PlannerClaude Opus 4.8anthropic.claude-opus-4-8One of threeNo
EmbeddingsCohere Embed v4cohere.embed-v4:0Not selectableFixed
RedactorThe planner modelWhatever the planner isFollows the plannerFollows the planner

What each role does:

  • Runner. The model behind agents and workflow workers, code analysis, document parsing and knowledge-graph building.
  • Planner. The model behind the coordinator, the Governor, workflow conditions and the semantic pass of PII redaction.
  • Embeddings. Every knowledge-graph write embeds text with Cohere Embed v4. There is no other choice.
  • Redactor. PII redaction's semantic pass uses the planner model. Choosing a planner chooses the redactor.

The inference zone prefix​

Bedrock serves these models through cross-region inference profiles that are zoned: a us zone and an eu zone. The wizard's Bedrock inference zone field is pre-selected from the account's region (us-* regions give us, eu-* regions give eu) and checked against the region at launch. When the deployment's configuration is written, every model id above receives that zone as a prefix. A deployment in an EU region therefore calls eu.anthropic.claude-sonnet-4-6, eu.anthropic.claude-opus-4-6-v1 and eu.cohere.embed-v4:0; a US deployment calls the us. forms. The zone is applied to all four roles together, so no model is called outside the deployment's zone. The supported regions and their zones are listed in Before you start.

Steps​

Enable model access before you deploy​

  1. In the target AWS account, open the Amazon Bedrock console in the deployment's region.
  2. Enable model access for Claude Sonnet 4.6, for the Claude Opus version you will choose (4.6 unless you change it), and for Cohere Embed v4.
  3. Wait until each shows as available.

The install job does not test model access. A deployment whose account lacks it still installs; the failure appears later, when Studio first calls the missing model.

Choose the models in the wizard​

In the wizard's Parameters section (Deploy your first Studio):

  • Leave Sonnet model id (runner) blank (shown as Automatic) to use Claude Sonnet 4.6, or select it explicitly. It is the only option.
  • Leave Opus model id (planner) blank (Automatic) to use Claude Opus 4.6, or select anthropic.claude-opus-4-7 or anthropic.claude-opus-4-8.

Change the models after install​

Models are set centrally for the deployment, not per agent or per user. To change them on a live deployment:

  1. Open Fleet Configurations and create or edit a template. Under Models (Override the shipped Bedrock model ids. Blank uses the shipped default for each.), set Sonnet model id and/or Opus model id.
  2. Open Update Manager and create a rule that points at the template and targets the deployment. The target preview lists the change, for example Opus model: anthropic.claude-opus-4-6-v1 → anthropic.claude-opus-4-8.
  3. When the rule fires, the job's Re-seed Bedrock model ids step writes the new ids with the deployment's zone prefix and the services restart.

The mechanics are the same as for a sizing change; see Infrastructure sizing and costs.

What you should see​

The deployment's Overview → Configuration lists Sonnet model, Opus model and Inference zone. A field that has not been recorded yet shows a hover explaining that wizard fields are recorded at launch and configuration fields when a reconfigure or upgrade applies them.

Notes​

  • Only the ids in the table are accepted. The wizard offers no other value, and the server refuses any other id in a template or draft.
  • The embeddings model is fixed. There is no field for it anywhere in the console.
  • Studio users cannot pick a model per agent or per conversation. The runner and planner are deployment-wide settings.
  • The inference zone must match the region. A template whose zone does not match a target deployment's region is skipped for that deployment (Skipped (zone mismatch) in the rule's history).
  • Bedrock model access is enabled per AWS account and per region. Enable it in the account and region the deployment uses.
  • Agents or knowledge-graph builds fail after a fresh install. Check model access in the Bedrock console for the deployment's region: all three of Claude Sonnet 4.6, the chosen Claude Opus version and Cohere Embed v4 must be enabled.
  • You changed the planner and redaction behaves differently. The redactor is the planner; a planner change is a redactor change.
  • The Overview shows a model you did not choose. Blank fields take the shipped default: Claude Sonnet 4.6 and Claude Opus 4.6.
  • An Update Manager rule skipped the deployment with a zone mismatch. The template's Inference zone field names a zone the deployment's region cannot serve. Leave that field blank in a template that targets deployments in more than one zone.