Skip to main content

Fleet configurations and Update Manager

For Owners and Operators updating Studio deployments: a Fleet Configuration Template names the release and configuration your deployments should be on, and an Update Manager rule applies it on a schedule. Anyone with fleet read access can read templates, rules and history.

Before you start: both screens are under Fleet Management. Create the template first; New Update Manager Rule is disabled until one exists.

Create a Fleet Configuration Template​

Open Fleet Configurations and click New Fleet Configuration Template.

SectionFieldValues
Name, DescriptionUp to 100 and 500 characters.
What this deploysDeploysStudio, stated as a fact: a template deploys Studio only.
Environmentdev, staging or prod; required ("Choose an environment").
Which releaseRelease version"Versions from the AlphaAgent catalogue. A version is mirrored into your organisation the first time a job uses it." Only the latest stable Studio release is offered, pre-selected and its option starts "Default: <version>"; required (see Which Studio release you can choose).
SizingSizing profile"Default: standard" first, then xs, small, large, xlarge.
Redis node type"Default: cache.t4g.medium" first, then the other node types your organisation offers.
ModelsCoordinator model (most capable), Worker model, Chat-title model (fastest, lowest cost)The same pickers as the wizard, each listing only its own class's model and starting on "Default: Claude Opus 5.5 · anthropic.claude-opus-5-5" (and the Sonnet 5.5 and Haiku 5.5 equivalents). A template names all three (Supported models).
Data protectionPII redaction defaultOff, Mask or Hash; required ("Choose a PII redaction default"). Workflows and runs can tighten it, never loosen it.
Network access"Templates carry no network settings and apply to every deployment. Each deployment keeps the network access it was created with: Private, or Public (CloudFront, existing)."

The preview reads "This template will set N field(s)" and lists each value as it will be stored, a default as "Default: <value>". Click Create. A template never carries an account, region, inference zone, certificate, sign-in domain prefix, network settings or trusted certificate authorities; those belong to the deployment, and the zone follows each deployment's region.

No field stores a blank: a field with a default stores the concrete value its default option names, and Environment, the release and the PII redaction default must be chosen. Saving refuses a missing choice with "Choose a value for Environment." (or Release, or PII redaction default), and a model its class does not take, such as a Claude 4.x id in a version saved before Organisations 1.1.0, with "The Coordinator model must be anthropic.claude-opus-5-5." (or the Worker or Chat-title model). The server applies the same rules on save and when a rule applies the template, and refuses a template that names the minimal stack (payload_template_minimal_not_supported: "A Fleet Configuration Template deploys Studio only.").

Edit opens the same modal; saving increments the template to version N+1. A rule still pinned to vN "stops applying until an admin adopts" the new version: its scheduled runs are skipped as Template edited, not adopted until you click Adopt vN on the rule. The list shows Name, Description, Version, Release, Rules and Updated. Delete warns when rules still use the template: they are stranded until pointed at another template.

A template is applied in two places: the deployment wizard's Start from a template section, where "<name> (vN)" pre-fills the draft and every field stays editable (Deploy your first Studio); and an Update Manager rule.

Create an Update Manager rule​

Open Update Manager and click New Update Manager Rule.

  1. Name (up to 100 characters).
  2. Fleet Configuration Template: pick "<name> (vN)"; the rule pins that version.
  3. Deployments: search and tick the targets, page by page (selections are kept across pages; Select all covers the page shown). Each one reads "<name> (<account>, <region>) · Private" (or "Public (CloudFront, existing)") " · Outbound: NAT gateway" (or "Transit Gateway"): one rule may cover private and existing public deployments, and each keeps its own network access through every job. The preview reads "This rule will affect N deployment(s)" and, per deployment, "<current release> → <target>" or "(already on target version)" plus any configuration difference (Sizing, Redis, Coordinator model, Worker model, Chat-title model), for example "Coordinator model: anthropic.claude-opus-4-6-v1 → anthropic.claude-opus-5-5". A Redis change briefly fails over the cache; a sizing change restarts every service.
  4. Schedule: the builder offers Frequency (Daily, Weekly, Monthly), Day, Day of month (1 to 28) and Time (UTC) as HH:MM, and confirms the sentence with the next three firings. Advanced accepts rate(<n> minutes|hours|days) or a cron(...) with exactly five fields: minute hour day-of-month month day-of-week.
  5. Maintenance window: tick Only fire during a maintenance window and set Start (UTC) and End (UTC) on the hour; the end is exclusive, a start after the end wraps past midnight, and a firing outside the window is deferred to the next one.
  6. Enabled: off until you tick it. Click Create.

Refusals name the rule broken: a missing name, template, deployment or schedule; a malformed rate or cron; an incomplete time; a window whose start and end hours are equal. A rule from an earlier release that used a filter shows a banner and switches to an explicit list on save.

The list shows Name, Fleet Configuration ("<template> (vN)" with Adopt vN when a newer version exists), Scope, Schedule, Maintenance window ("HH:00 to HH:00 UTC" or "Any time"), Enabled, Next run, Last run, and Edit, History and Delete. Adopt vN warns that matching deployments restart every service in one rolling upgrade, interrupting anything mid-flight such as a knowledge graph still building. Delete leaves deployments the rule already upgraded unaffected.

Read a rule's History​

History shows one card per firing: Fired, Nothing to do, Drift found, not applied, Deferred (outside window), Template missing or Template edited, not adopted. A firing that started jobs lists "Triggered: <deployment> (<status>)" and any skips: "Skipped (paused)", "Skipped (job in flight)" or "Skipped (zone mismatch)". A private deployment whose template names a release older than 2.0.15 is not updated, and the firing says so: "Not updated, because Private network access needs Studio 2.0.15 or later: <names>." The same applies to a deployment with trusted certificate authorities, and, for any deployment, to an update to a release before 2.0.20 or a model change on a deployment that still runs one: "Not updated, because Claude 5.5 models need Studio 2.0.20 or later: <names>." (Supported models). A template whose models are not the supported set reads "Not updated, because this template's models are not a supported set for: <names>." A preflight warning about a model agreement or a Bedrock quota is recorded on the firing and does not stop the update. A deployment that keeps failing is flagged "has failed N job(s) in a row". Load more pages back.

What a roll does​

When a rule fires and a target is off the template's release or configuration, it starts an Upgrade job on that deployment. The job runs preflight, captures a restore point, shows the Studio maintenance page to users, updates the core, writes the three model ids for the deployment's zone (the template's, or the defaults) with every service's copy of the Worker model id, re-seeds the configuration and trusted certificate authorities, pushes and verifies images, updates the web app, the stateless stack (and the edge stack of an existing public deployment), re-applies a private deployment's network stack with its recorded ranges, updates the compute stack and the task definitions, waits for the services to settle, restores the normal Studio app, runs the doctor and records the new release. On a live walk a rule fired at its scheduled minute and rolled two Studios to the next release in 47 minutes, 17 steps each, with the maintenance page shown meanwhile. The Fleet's Version column reads "<current> → updating to <target>" throughout.

If an update fails after it has started, the deployment is rolled back to the restore point that update captured, and the job reads Rolled back; a job that failed before it captured one changed nothing and is not rolled back. To undo an update that completed, use Roll back… beside Version on the deployment's Overview (Deployment detail): it returns the services to the restore point the last completed update or configuration change captured, the job is followed in Jobs, and the action is recorded in Audit. Three failures cover the edges, listed on Failure codes: no_restore_point, rollback_failed and restore_point_unwritable.

What you should see​

  • After a firing: an Upgrade job in each targeted deployment's Jobs view, the Fleet's Version column reading "<current> → updating to <target>", and History showing Fired with "Triggered: <deployment> (<status>)".
  • When it finishes: every targeted row on the template's release, Healthy, with Last job pointing at the upgrade.

Which Studio release you can choose​

Your Organisation installs and upgrades to the latest stable Studio release only. The New deployment wizard, Fleet Configuration Templates, Update Manager rules and upgrades all offer and accept just that release.

  • Naming an older release is refused, and the message names the latest: "Studio 2.1.1 is not the latest release. Only the latest Studio release, 2.1.3, can be installed or upgraded to." followed by what to do next (choose the latest and try again).
  • Rollback still returns a deployment to its previous release, and so does the automatic rollback after a failed update. Re-applying the release a deployment already runs is also allowed.
  • A template or rule pinned to an older release is not changed for you. Opening the template shows "This named Studio <older>. Only the latest Studio release, <latest>, can be installed or upgraded to, so it is selected below. Save to move to it." Saving stores the latest as the next template version. A rule on an older release is skipped and says "This rule applies Studio <older>, which is not the latest release": save the template with the latest, then adopt that template version in the rule.
  • The setting is ORG_STUDIO_RELEASE_POLICY in the Organisation's common-config secret. It is latest-stable by default; any restores choosing any release the catalogue offers. An Organisations upgrade keeps the value an administrator set.
  • If the AlphaAgent Console catalogue cannot be read, the latest cannot be confirmed and the release is refused; try again in a few minutes.
  • In the AlphaAgent Console, the Organisation bundle card shows only the latest Organisations release. See Release notes for every release.

Notes​

  • Sizing profile, Redis node type and the three models are not editable on the deployment's Overview: save them in a template and point a rule at it, or adopt the new template version on an existing rule. A model change always writes all three classes together.
  • Rules have no run-now button. To update one deployment straight away: create a rule scoped to that deployment with Advanced schedule rate(5 minutes), no maintenance window, Enabled; History shows Fired within five minutes; disable or delete the rule once the Upgrade job has started.
  • A rule skips a paused deployment, one with a job in flight, and one whose inference zone does not match a template that names one (only a template saved through the API or before Organisations 1.1.0 can; the editor has no zone field).
  • Template edited, not adopted: click Adopt vN. Template missing: edit the rule and choose another template. Deferred (outside window): it tries at the next firing inside the window.
  • The wizard refuses a template authored for an older form: re-save it from Fleet Configurations.
  • A template version saved before Organisations 1.1.0 can name a Claude 4.x model, the minimal stack or a blank field. Open it with Edit: each field now shows the value it will store; choose the models, the release, the Environment and the PII redaction default, save it as the next version and Adopt vN on its rules.