Generated banner for Agent Advisor
Generated logo for Agent Advisor

Agent Advisor

AWSOfficialPublished by AWS

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, I have an agent idea what do I build, move/migrate my agents to AWS, agent migration plan, add AgentCore services (memory, gateway, identity, policy, observability) to an agent already on AWS, Temporal on AWS (migrate/run Temporal workers on AWS, a service orchestrated by Temporal, Temporal Cloud vs self-hosted). Temporal Workflow code is never rewritten into Step Functions. Requires at least one agentic component — a purely non-agent system (plain services, batch jobs, HTTP endpoints, non-agent Temporal Activities) is out of scope, redirected to gcp-to-aws / heroku-to-aws / llm-to-bedrock. Not for: compute/data migration with no AI agent; pure LLM SDK rewrite (use llm-to-bedrock); per-model pricing.
— the description by AWS

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Agent Advisor provides a structured, multi-phase workflow to help users determine the optimal AWS runtime for their AI agents. It uses a deterministic scoring engine to evaluate requirements and guides users through a process that includes discovery, architectural design, cost estimation, and the creation of an executable proof-of-concept. The skill supports various AWS compute options, including AgentCore, ECS, EKS, and Lambda, and integrates with migration engines for existing workloads.

What it does

  • Recommends AWS runtimes for AI agents based on technical requirements.
  • Generates migration plans for existing AI workloads moving to AWS.
  • Provides architectural guidance for agentic systems.
  • Assembles executable proof-of-concept scaffolding.
  • Estimates coarse cost magnitudes for proposed agent deployments.
  • Integrates with external migration engines for workload transitions.

When to use it

  • When you need to decide which AWS runtime is best for a new AI agent.
  • When migrating an existing AI agent workload to AWS.
  • When you need to add services like memory, identity, or observability to an existing AWS agent.
  • When you require a structured plan and POC for deploying agents on AWS.

Advantages

  • Provides a deterministic, repeatable recommendation process.
  • Supports a wide range of AWS compute environments.
  • Offers a unified flow from initial idea to executable POC.
  • Adapts to both technical and business-focused user backgrounds.

Usage examples

“I have an agent idea, what do I build?”
The agent initiates the intake process to clarify your requirements and recommend an appropriate AWS architecture.
“Move my agents to AWS.”
The agent triggers the migration workflow to assess your existing workload and plan the transition to an AWS runtime.
“Which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda?”
The agent runs a scoring analysis to compare these runtimes against your specific agentic needs.
“Add AgentCore services to an agent already on AWS.”
The agent enters the add-capabilities branch to guide you through integrating memory, gateway, and observability services.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/aws/agent-advisor/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip agent-advisor.zip -d .agents/skills

Documentation by AWS

AWS Agent Advisor

Helps startups decide how and where to run AI agents on AWS. Deterministic scoring recommends a runtime; the conversation adapts to the user's technical background.

Definitions

  • "Load" = Read the file with the Read tool and follow it. Do not summarize or skip.

  • $RUN_DIR = the run directory under .agent-advisor/ (e.g. .agent-advisor/0630-1430/), created in Intake.

  • $PLUGIN = ${CLAUDE_PLUGIN_ROOT} (the installed plugin root). On Claude Code this token substitutes inline. If ${CLAUDE_PLUGIN_ROOT} does not resolve (some Cursor/Codex builds, or a literal ${CLAUDE_PLUGIN_ROOT} string showing up in a path error), fall back to the skill's own directory: this SKILL.md lives at <plugin>/skills/agent-advisor/SKILL.md, so the engine and its data are all inside this skill — scripts at ./scripts/..., runtime profiles at ./references/runtimes/..., and decision refs at ./references/decision-refs/... relative to it. Prefer ${CLAUDE_PLUGIN_ROOT}/skills/agent-advisor/...; use the relative fallback only when it fails to resolve.

Prerequisites

Phase Structure (frontmatter)

Phase, fragment, and assembler files carry a YAML frontmatter block that declares how each phase is composed — its inputs, triggers, fragments, assembler, artifacts, gates, and ordering. The execution contract is the vendored references/vendored/dsl/INTERPRETER.md: it defines every frontmatter key, the fragment/assembler model, the gate protocol (HANDOFF_OK / GATE_FAIL), and the interpreter loop. Load it first (once, at the start of a run), then execute each phase file's prose body. Elsewhere in this skill, INTERPRETER.md (without a path) refers to this loaded contract.

Execution

This skill is driven by the interpreter loop in INTERPRETER.md (§ The interpreter loop): it reads .phase-status.json, determines the current phase, runs each phase's _preconditions / fragments / _assemble / _postconditions, advances on HANDOFF_OK via _advances_to, and validates state. The backbone (intake → discover → clarify → confirm → design → estimate → generate → migration-plan → poc → complete) and the one sidebar branch (add-capabilities) are derived from the phase files' frontmatter — they are not restated here.

Cold start (entry phase). With no run under .agent-advisor/ carrying a .phase-status.json, begin at references/phases/intake/intake.md — this skill's entry phase (the one carrying _init: true). On a warm start, current_phase in .phase-status.json is authoritative (INTERPRETER.md § The interpreter loop).

Skill bindings (INTERPRETER.md § Skill bindings). This skill declares:

  • Run root: .agent-advisor/ — $RUN_DIR is this skill's name for the run directory (.agent-advisor/[MMDD-HHMM]/). Intake's own prose performs the _init bootstrap.

  • State shape: § State file below (advisor-specific keys such as entry_point, audience, recommendation_reviewed, migration_plan_ctx, migration_plan_unavailable); the shared state schema is not vendored.

  • Run seed (optional): $RUN_DIR/seed.json, else .agent-advisor/seed.json at the run root (schema scripts/schemas/seed.json) supplies machine-readable answers for a non-interactive run — the Clarify dimensions, the two gate answers, the POC mode, the live-probe answer, and a co_recommend tie-break. It is the HIGHEST-precedence source for every value it carries (clarify.md Step 2.5), which is what makes a repeated run's score comparable: the deterministic engine gets byte-identical input. A gate the seed omits is declined; a dimension the seed omits falls through to detection, then prose, then an assumed value that MUST be recorded in $RUN_DIR/UNANSWERED.md. With no seed, the interactive flow is unchanged.

  • Resolved statuses: skipped (routing resolved the phase without running it), plus not_applicable for migration_plan only.

  • Conditional backbone routing: the entry-point routing below. When a routing rule marks a phase not-applicable, set it skipped and advance through its _advances_to in the same state write.

Routing & gates (orchestration)

Sidebar placement and conditional backbone routing are orchestration prose owned by this file (INTERPRETER.md § Skill bindings, § Backbone vs sidebar).

Entry-point routing:

  • build_scratch → skip Discover; Clarify → Confirm → Design → Estimate → Generate → Gate 2 → POC (any winning runtime). No migration plan (nothing existing to migrate).

  • build_deploy → Discover (if code) → Clarify → Confirm → Design → Estimate → Generate → Gate 1 → Migration Plan (if existing non-AWS AI workload detected and user confirms) → Gate 2 → POC (any winning runtime).

  • migrate → Discover (if code) → Clarify → Confirm → Design → Estimate (target-state run cost; migration TCO comparison stays with the Migration Plan engine) → Generate → Gate 1 → Migration Plan (in-skill, reusing the sibling gcp-to-aws skill) → Gate 2 → POC (any winning runtime, when the plan was produced). Declining Gate 1 keeps the classic handoff: pointer to /aws-startup-advisor:llm-to-bedrock with handoff-summary.md.

  • add_capabilities → load references/phases/add-capabilities/add-capabilities.md and follow it (no runtime scoring; writes capabilities-recommendation.md). This is a self-contained branch — it does NOT pass through Clarify / Confirm / Design / Estimate / Generate, so the phase gate below never applies to it.

  • Temporal detection routes into migrate with temporal units pre-seeded (see discover).

Gate semantics (backbone tail):

  • Gate 1 → migration_plan runs only when generate is done AND recommendation_reviewed == true (generate.md Step 5.5) AND entry point ∈ {migrate, build_deploy} AND the run is migration-eligible (generate.md Step 6) AND the user confirmed Gate 1. Otherwise resolve it: not_applicable (build_scratch / no migratable workload) or skipped (declined) — and advance.

  • Gate 2 → poc runs only when phases.poc == "in_progress" (set when the user answers Gate 2 "yes" — asked in generate.md Step 7 or migration-plan.md Step 6) AND recommendation_reviewed == true. Any winning runtime (agentcore / ecs / eks / lambda / lambda_microvms) — the POC shape follows the verdict (poc.md Step 3 dispatch on references/decision-refs/poc-shapes.md). Gate 2 is only offered when migration_plan ∈ {completed, skipped, not_applicable} — or in_progress on build_deploy only (Stage 2 failed/aborted; fallback POC from design.json per migration-plan.md failure handling); for entry point migrate, only when migration_plan == "completed" (the POC implements the plan) OR when the stage resolved not_applicable with migration_plan_unavailable == "engine_absent" — a standalone deployment that does not bundle the migration engine, where Gate 2 is offered by migration-plan.md Step -1 and the POC is design-backed. A migrate-POC with no plan for any OTHER reason (the user declined) has nothing to implement.

  • Persisting Gate 2 as phases.poc = "in_progress" BEFORE poc.md loads makes the confirmation resumable: if the session breaks between the "yes" and the load, the interpreter re-enters poc without re-asking. (A declared deviation from INTERPRETER.md § The interpreter loop step 5's gate-then-in_progress ordering — the user's confirmation is the entry event worth persisting.)

Phase gate: Do NOT load design.md / estimate.md / generate.md unless $RUN_DIR/.phase-status.json exists and BOTH phases.clarify == "completed" AND phases.confirm == "completed". Confirm confirms the deployment model, the service set, and (for a co_recommend tie) the user's chosen_runtime — Design and the diagram depend on its confirm.json output, so it must not be skipped. If the user asks to skip Clarify or Pass 2, refuse briefly and run it.

State file (.phase-status.json)

{
  "run_id": "0630-1430",
  "entry_point": "build_scratch",
  "audience": "technical",
  "current_phase": "clarify",
  "phases": {
    "intake": "completed",
    "discover": "skipped",
    "clarify": "in_progress",
    "confirm": "pending",
    "design": "pending",
    "estimate": "pending",
    "generate": "pending",
    "migration_plan": "pending",
    "poc": "pending"
  }
}

Status values: pending → in_progress → completed, plus skipped. Use read-merge-write: read before each update, change only the advancing keys, keep prior phases.

recommendation_reviewed (top level, boolean) is set to true by generate.md Step 5.5 when the user explicitly confirms they have seen the recommendation. Gate 1, Gate 2, and the migration_plan / poc states all require it — no gate may be asked while it is absent.

migration_plan additionally uses not_applicable (build_scratch, or no migratable workload detected). When Stage 2 runs, migration_plan_ctx is added at the top level: {"repo": "<abs path to target repo>", "migration_dir": "<abs path to .migration/<id>/>"} — Stage 3 reads gcp-to-aws artifacts ONLY via this recorded path, never by re-globbing.

Files

FilePurpose
references/vendored/dsl/INTERPRETER.mdVendored DSL execution contract (interpreter loop + gate protocol)
references/phases/intake/intake.mdEntry point + technical background + open context
references/phases/discover/discover.mdLightweight code detection
references/phases/clarify/clarify.mdClarify orchestrator + answer mapping to scoring keys
references/phases/clarify/clarify-technical.mdTechnical-background question wording
references/phases/clarify/clarify-business.mdBusiness-background question wording
references/phases/confirm/confirm.mdWinner-specific follow-ups
references/phases/design/design.mdAssemble recommendation; Migrate handoff branch
references/phases/estimate/estimate.mdCoarse cost magnitude
references/phases/generate/generate.mdLayered recommendation doc + scaffolding
references/phases/migration-plan/migration-plan.mdStage 2: full migration plan via the sibling gcp-to-aws engine
references/decision-refs/temporal.mdTemporal rules: Tier 1/2 tables, adapter, runbooks, commercials (consumed by discover/clarify/design/generate)
references/decision-refs/poc-shapes.mdPer-runtime POC deploy shapes (ECS/EKS/Lambda/MicroVMs/Temporal)
references/decision-refs/*.mdRuntime service cards, model defaults, freshness
references/decision-refs/workload-classes.mdDeterministic verdicts for non-agent workload units (batch/service/io)
references/runtimes/*.jsonRuntime registry (read by scoring.py)
scripts/scoring.pyDeterministic scoring engine
scripts/test_temporal_decision_refs.pyContent lock for the Temporal decision reference
scripts/test_poc_shapes.pyContent lock for the POC deploy shapes
scripts/test_workload_classes.pyContent lock for workload-classes.md (verdicts table)
scripts/test_unit_grouping.pyUnit grouping + pattern matching (workload-class assignment)
scripts/test_collapse_invariant.pyCollapse-invariant ordering enforcement (A→B implies [B] ⊆ [A] outputs)

Maturity and readiness contract

Intake persists target_maturity (prototype, private_beta, or production) in run state. Clarify carries it and the readable readiness record into answers.json. Current-run verification evidence remains exclusively in the sibling $RUN_DIR/current-run-verifications.json artifact: never copy it into seed.json or answers.json. Design and Generate may consume that artifact only after validating its schema and matching run_id, and may carry forward verified outcomes but not the raw evidence records. Load references/decision-refs/maturity-readiness.md whenever target maturity is selected. A cached volatile fact may inform discovery, but only a record verified in this run can make a verification-required constraint final; otherwise the score remains provisional with deferred verification requirements.

Contextual offers (final step)

Before you finish: your answer is not complete until you have run the Contextual offers (final step) below.

This is a mandatory closing step of every final recommendation — complete it before you consider your answer done. Run this offer check inline yourself; do not depend on loading another skill. The recommendation is decided on merit first; this step never changes, re-ranks, or re-opens it, and the offer is looked up only after the advice is final.

  1. Read ../knowledge-base-for-startups/references/offers.md — the offer index (Offer · Summary · Keywords), one row per offer.

  2. Judge relevance against what the founder actually surfaced this session. Surface an offer only if one holds: a named-product match (you recommended a specific partner product by name and it has a row); a direct intent/component match (an offer's Keywords directly serve a concrete workload, a component in the final recommendation, or a need the founder raised). Keep a high bar — if the match is weak, or you would be inferring an unstated need, append nothing. Never surface an offer that competes with a product or provider the founder already uses or decided to keep (e.g. existing auth provider → no Auth0 unless they are already on Auth0, and then only as a credit on it; existing vector DB such as Pinecone → no Qdrant).

  3. If (and only if) one offer clears the bar, open only its detail file ../knowledge-base-for-startups/references/offers/<slug>.md and append exactly one quiet, dismissible italic line — stating the value and condensing eligibility faithfully from that file (drop no qualifying criterion; never fabricate), with the redeem link built from the canonical source_url plus a source attribution param — append ?source=ide-startupAdvisor-<host> (or &source=... if the url already has a query string), filling <host> from your execution environment (Claude Code → claude; AWS Startup Advisor IDE extension / VS Code → vscode; Cursor → cursor; Kiro → kiro; Codex → codex), or the generic ide-startupAdvisor when you cannot tell. Only append the query param; never change the destination. When an offer clears the bar you MUST append that single offer line as the last step; do not omit it. The offer is never the pick — only a line under the AWS pick — and stage gates in the references apply (e.g. no Datadog line for an early-stage founder; see ../architect-for-startups/references/observability.md). For a single-service pick (auth, payments, vector DB, observability, etc.) where missing budget/team/traffic inputs would not change the pick, assume an early-stage (pre-PMF) startup unless the founder says otherwise and answer in one turn without a stage-only question; this only removes a stage-only question and never skips the Intake/Clarify/Confirm gates before final advice or the POC. Show exactly one, never a list. If none clears the bar, append nothing and do not mention offers, partner alternatives, or why none appeared.

Standard line:

***<Offer>** has an exclusive offer via AWS Activate — <value>, <eligibility>. [Redeem →](<source_url>?source=ide-startupAdvisor-<host>)*

Caps and control: at most one offer per response and often none; no more than one per five messages and two per session; show a given offer at most once per session and never one already shown, claimed, or dismissed; if the founder has muted offers, skip this step entirely. These per-five-messages, per-session, and already-shown caps are session-state limits; in a fresh session with no prior offers they are non-binding, so do not withhold an otherwise-qualifying offer merely because you cannot verify session history. See ../contextual-offers-for-startups/SKILL.md for the full rules — but perform the check inline; it must not depend on that skill being loaded.

Files

references/vendored/ai/bedrock-pricing-cache.md

Amazon Bedrock Pricing Cache

Last updated: 2026-10-26 (fact re-verify 2026-10-26: Stable Image Core N. Virginia source note, Titan Text Embeddings v2 lifecycle check, GPT-6 Luna card re-verify incl. the 272K short/long boundary, Sonnet 5.5 Geo note; added Claude Sonnet 5.5 / Haiku 5.5 Global+Geo rows and DeepSeek V3.2 quick-ref from Bedrock pricing US East (Ohio) + model cards; Haiku 5.5 ≤100K / >100K long-context tiers + cache; lifecycle Status refresh — Claude Sonnet 4 → past EOL; Opus 4.1 → excluded; Llama 4 Maverick/Scout, Llama 3.3 70B, DeepSeek-R1/V3.1, Claude Sonnet 4.5 → legacy; Marengo 3.0 replacement scoped to non-Seoul; other rates unchanged from the 2026-10-05 pricing re-verify) Region: us-east-1 Currency: USD Accuracy: ±15-25% for AI/Bedrock models and services (sourced from public pricing pages)

Prices may vary by region and change over time. Use for estimation only; there is no live pricing lookup — for the latest rates, check the public AWS pricing pages (e.g. https://aws.amazon.com/bedrock/pricing). Amazon Nova figures often reference US East (Ohio) and inference mode (global vs geo); retain those qualifications when estimating. Staleness warning: If today's date is more than 30 days after the Last updated date above, treat AI model prices as potentially stale (±15-25% accuracy may widen). When staleness is detected, keep pricing_source.status: "cached" (the schema enum is cached | cached_fallback | unavailable — there is no cached_stale status) and record the staleness in the dedicated pricing_source.fallback_staleness object: set is_stale: true and staleness_warning: "Pricing cache is more than 30 days old — AI model prices may have changed. Verify against [aws.amazon.com/bedrock/pricing](https://aws.amazon.com/bedrock/pricing/)." Surface that same warning to the user in the estimate output.

Lifecycle is not a cached price field. The Status column below is a dated snapshot, not permission to skip the lifecycle check. Before selecting any model, call GetFoundationModel or ListFoundationModels and read modelLifecycle.status. For a model launched on or after 2026-09-07, also read its model card: its Legacy period may be 45 days rather than 6 months, and it will never appear in the Legacy/EOL table. See vendored/ai/ai-model-lifecycle.md.


Bedrock Models (On-Demand)

Opus selection policy: Recommend Opus 5.5 for new Opus migration targets. Opus 4.8 rates are retained for existing deployments only; do not recommend it as a new target or automatic fallback. The separately documented Opus 4.6 Batch exception remains.

Opus 5.5 rates verified: 2026-09-24. Source: AWS Price List API, service AmazonBedrockFoundationModels, filter servicename = Claude Opus 5.5 (Amazon Bedrock Edition) and the source regionCode; see Bedrock pricing. The Opus 5.5 rows below are Standard on-demand, per 1M tokens: Global $4/$20; commercial Geo and Mantle in-region $4.40/$22; GovCloud $4.80/$24. For example, us-east-1 input/output SKUs are KVG5FBPDJPKF5TJY / MWH4TD2A4D5CEBAP (Global) and J9QFZT8WAQABG9ZX / FCRGDQ596BG7EQKH (Geo/Mantle). The model card lists Active lifecycle, 1M context, 128K output, and no Batch. Runtime uses us./eu./au./jp. Geo or global. CRIS, or the bare ID in eu-west-2 (in-region model-card and pricing verification: 2026-10-03); Global is not available in GovCloud. Mantle uses the bare ID only in us-east-1, ap-southeast-4, and us-gov-west-1. Choose the price row by region and inference profile; a generic model name alone is insufficient. Other cache rows retain the full-cache date at the top of this file.

Anthropic Claude (Standard on-demand) figures below match US East (N. Virginia) on Amazon Bedrock pricing as of cache refresh. Recommend defaults (new migrations): Claude Sonnet 5 (flagship), Claude Opus 5.5 (demanding reasoning), Claude Haiku 5.5 (cost/speed). Do not default to any Claude Fable / Mythos frontier model (Fable 5, Fable 5.1, and successors). Claude Fable 5 and Claude Fable 5.1 (GA Sep 1, 2026) are the most expensive Anthropic models (Mythos-class). Fable 5 is $10/$50 per 1M tokens, Global/base. Fable 5.1 is served via CRIS only (no in-region/bare-id form), with two supported profiles: Global (global.anthropic.claude-fable-5-1) at $10/$50 — supported from commercial us-east-1 and a real option when there is no residency constraint — and Geo US (us.anthropic.claude-fable-5-1) at $11/$55 (~10% above Global), for workloads with US-only residency requirements. Quote whichever profile matches the actual deployment target; do not default to Geo pricing for a Global deployment. Fable 5.1's cache read is $0.25 (Global; 0.025x of Global input) or $0.275 (Geo); Fable 5's cache read is $1.00 (Global). Bedrock lists no batch rate for either. Both are Anthropic Covered Models: using them requires opting the account into the aws_review data-retention mode. In-region (non-CRIS) access for Fable 5.1 exists only in AWS GovCloud (US). Claude Mythos 5.1 is a gated Preview for vetted cyber/bio research organizations and is not a migration target. Claude Opus 4.8 keeps the same $5/$25 rate as Opus 4.6/4.7. Claude Sonnet 5 launched June 30 at $2/$10; that launch rate became the standard price on Sep 1, 2026 (the scheduled increase to $3/$15 was cancelled), so Sonnet 5 is now both newer and cheaper than Sonnet 4.6 ($3/$15). Claude Opus 4.7 lists the same headline on-demand input/output as Opus 4.6 on that page; confirm batch availability per model (Opus 4.7 batch was not listed on the global cross-region table when this row was added). Claude Opus 4.1 entered Legacy on Jul 8, 2026 (EOL Jan 8, 2027). Batch, prompt cache (5m / 1h write + cache read), and geo / in-region cross-region rows on that page can differ; e.g. US East (Ohio) cross-region inference for Claude Sonnet 4.6 is listed at $3.30 / $16.50 per 1M input/output (≈10% above N. Virginia). Long-context SKUs do not all use the same multiplier: Sonnet 4.6 and Opus 4.6 long-context modes share the same on-demand rates as the non–long-context rows on the standard table; Sonnet 4.5 and Sonnet 4 long-context rows are priced higher on that same table.

Geo vs. Global inference pricing. Sonnet 5, Opus 4.8, Sonnet 4.6, and Haiku 4.5 cannot be invoked on-demand with their bare model ID in US regions on bedrock-runtime — they require a cross-Region inference profile ID there (see llm-to-bedrock/references/helpers/bedrock-known-fixes/references/bedrock-inference-profile-model-id.md). This is per-model and per-region, not universal: Haiku 4.5's model card states the bare ID is never supported for on-demand throughput on any bedrock-runtime region. Sonnet 5 and Sonnet 4.6, by contrast, DO support true in-Region (bare-ID) invocation — but only from eu-west-2 (London); every US region (and every other region checked) shows In-Region unsupported for both models. Opus 4.8 behaves like Haiku 4.5: no in-Region support anywhere. Confirm the target model's actual In-Region/Geo/Global support table on its model card before assuming either outcome.

The Geo profile (us./eu./au./jp./in. prefix) carries a ~10% price premium over Global (global. prefix) — the US East (Ohio) cross-region row cited above for Sonnet 4.6 ($3.30/$16.50) is this same Geo premium. AWS documents Global cross-Region inference as saving "approximately 10%... compared to geographic cross-Region inference." The table below's bare-id rows are the Global/base rate; for a Geo (us.-prefixed) deployment, multiply input/output by 1.10 — Sonnet 5 and Sonnet 5.5 Geo are $2.20/$11.00 (Sonnet 5.5 Geo is listed directly on the pricing table, not derived), Opus 4.8 Geo is $5.50/$27.50, Sonnet 4.6 Geo is $3.30/$16.50, Haiku 4.5 Geo is $1.10/$5.50. llm-to-bedrock/scripts/bedrock_pricing.py's STATIC_FALLBACK table keys the us. id to the Geo rate and the bare id to the Global/base rate — read from that table, not this one, when a migration plan pins a specific inference profile.

Opus 5.5 rows already specify Global, Geo, Mantle, London or GovCloud pricing; do not apply another 1.10 multiplier.

Sonnet 5.5 / Haiku 5.5 (anthropic.claude-sonnet-5-5 / anthropic.claude-haiku-5-5 on Bedrock), rates verified 2026-10-25. Source: Amazon Bedrock pricing, Anthropic models table, Global and Geo/In-region Cross-region Inference, US East (Ohio); model cards confirm Active lifecycle and 1M context. Per 1M tokens — Sonnet 5.5 Global: input $2.00, output $10.00, 5m cache write $2.50, 1h cache write $4.00, cache read $0.10; Geo (US): $2.20 / $11.00, 5m $2.75, 1h $4.40, cache read $0.11. Haiku 5.5 uses tiered long-context pricing at a 100,000-token prompt boundary (model card; Bedrock pricing "Claude Haiku 5.5 - Long Context" row). Prompt length counts all input tokens including cache reads and cache writes. When the prompt exceeds 100,000 tokens, the higher Long Context rates apply to the whole qualifying request (input, output, and cache read/write) — not only the tokens past the boundary. Per 1M tokens — ≤100K Global: input $0.10, output $0.50, 5m cache write $0.125, 1h cache write $0.20, cache read $0.01; US Geo: $0.11 / $0.55, 5m $0.1375, 1h $0.22, cache read $0.011. >100K Global: $0.50 / $2.50, 5m $0.625, 1h $1.00, cache read $0.05; US Geo: $0.55 / $2.75, 5m $0.6875, 1h $1.10, cache read $0.055. When per-request prompt size is unknown, do not silently quote the ≤100K row — follow the existing unavailable / dual-scenario handling in estimate-ai.md (flag pricing_tier: "approximate — request-size distribution unknown" and present both ≤100K and >100K rows, or set pricing_source: "unavailable"). Batch is N/A for both Sonnet 5.5 and Haiku 5.5. Cache-read note: Sonnet 5.5 cache read is reduced 50% from the prior rate starting October 7, 2026 (prior Global $0.20). Sonnet 5 keeps its own $0.20 Global cache-read row. Do not silently reuse Sonnet 5 or Haiku 4.5 rates for 5.5 estimates. Read the Sonnet 5.5 migration guide before recommending Sonnet 5.5 request/response handling.

GPT-6.1 Terra rates verified 2026-11-02. Source: AWS model card. The quick-reference row is Standard pricing for requests with at most 272,000 input tokens, using Mantle in-region in us-east-1 or runtime US Geo CRIS. Global CRIS is $1.00/$5.00 per 1M input/output tokens. Above 272,000 input tokens, reprice the full request: In-Region/US Geo $2.20/$8.25, Global $2.00/$7.50. The context window is 1,050,000 tokens, not 272K. Cache write/read rates per 1M tokens are $1.375/$0.055 (short In-Region/Geo), $1.25/$0.05 (short Global), $2.75/$0.11 (long In-Region/Geo), and $2.50/$0.10 (long Global). Cache writes retain the prefix for 30 minutes. These rates already include the applicable inference-option premium; do not apply another 1.10 multiplier. If request-size distribution is unknown, show both context scenarios or mark the estimate unavailable. Source-provider prices require separate verification; do not infer them from these Bedrock rates.

Multi-provider quick reference (per 1M tokens)

See vendored/ai/ai-model-lifecycle.md for lifecycle details. Do not recommend Legacy models for new migrations. Rows whose Status is restricted (…) are never recommended_model / backup_model and never a default (Covered Models, gated previews).

ModelModel IDProviderInput $/1MOutput $/1MContextTierStatus
Claude Fable 5anthropic.claude-fable-5Anthropic10.0050.001Mfrontierrestricted (Covered Model; aws_review opt-in)
Claude Fable 5.1global.anthropic.claude-fable-5-1Anthropic10.0050.001Mfrontierrestricted (Covered Model; aws_review opt-in; CRIS only; Global rate shown — see note below for the us. Geo alternative at $11/$55)
Claude Sonnet 5anthropic.claude-sonnet-5Anthropic2.0010.001Mflagshipactive ($2/$10 made the standard price Sep 1, 2026)
Claude Sonnet 5.5 (Global)global.anthropic.claude-sonnet-5-5Anthropic2.0010.001Mflagshipactive (Global CRIS; ACTIVE per model card; source US East (Ohio) pricing table)
Claude Sonnet 5.5 (US Geo)us.anthropic.claude-sonnet-5-5Anthropic2.2011.001Mflagshipactive (US Geo; source US East (Ohio) pricing table)
Claude Opus 5.5 (Global)global.anthropic.claude-opus-5-5Anthropic4.0020.001Mpremiumactive (Global CRIS; no Batch; verified 2026-09-24)
Claude Opus 5.5 (US Geo)us.anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (commercial US Geo; no Batch; verified 2026-09-24)
Claude Opus 5.5 (EU Geo)eu.anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (EU Geo; no Batch; verified 2026-09-24)
Claude Opus 5.5 (AU Geo)au.anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (AU Geo; no Batch; verified 2026-09-24)
Claude Opus 5.5 (JP Geo)jp.anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (JP Geo; no Batch; verified 2026-09-24)
Claude Opus 5.5 (Mantle)anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (commercial Mantle Messages; no Batch; verified 2026-09-24)
Claude Opus 5.5 (London in-region)anthropic.claude-opus-5-5Anthropic4.4022.001Mpremiumactive (eu-west-2 runtime only; no Batch; verified 2026-10-03)
Claude Opus 5.5 (GovCloud Geo)us.anthropic.claude-opus-5-5Anthropic4.8024.001Mpremiumactive (us-gov-east-1/us-gov-west-1 only; no Batch; verified 2026-09-24)
Claude Opus 5.5 (GovCloud Mantle)anthropic.claude-opus-5-5Anthropic4.8024.001Mpremiumactive (us-gov-west-1 Mantle only; no Batch; verified 2026-09-24)
Claude Opus 4.8anthropic.claude-opus-4-8Anthropic5.0025.00200Kpremiumactive
Claude Sonnet 4.6anthropic.claude-sonnet-4-6Anthropic3.0015.00200Kflagshipactive
Claude Sonnet 4.6 — Long Contextanthropic.claude-sonnet-4-6Anthropic3.0015.00200K+flagshipactive
Claude Opus 4.6anthropic.claude-opus-4-6-v1Anthropic5.0025.00200Kpremiumactive
Claude Opus 4.6 — Long Contextanthropic.claude-opus-4-6-v1Anthropic5.0025.00200K+premiumactive
Claude Opus 4.5—Anthropic5.0025.00200Kpremiumactive
Claude Sonnet 4.5anthropic.claude-sonnet-4-5-20250929-v1:0Anthropic3.0015.00200Kflagshiplegacy (EOL Apr 8, 2027)
Claude Sonnet 4.5 — Long Contextanthropic.claude-sonnet-4-5-20250929-v1:0Anthropic6.0022.50200K+flagshiplegacy (EOL Apr 8, 2027)
Claude Haiku 4.5anthropic.claude-haiku-4-5-20251001-v1:0Anthropic1.005.00200Kfastactive
Claude Haiku 5.5 (Global)global.anthropic.claude-haiku-5-5Anthropic0.100.50≤100Kfastactive (Global CRIS; ≤100K prompt)
Claude Haiku 5.5 (Global) — Long Contextglobal.anthropic.claude-haiku-5-5Anthropic0.502.50100K+fastactive (Global CRIS; >100K prompt — whole request at LC rates)
Claude Haiku 5.5 (US Geo)us.anthropic.claude-haiku-5-5Anthropic0.110.55≤100Kfastactive (US Geo; ≤100K prompt)
Claude Haiku 5.5 (US Geo) — Long Contextus.anthropic.claude-haiku-5-5Anthropic0.552.75100K+fastactive (US Geo; >100K prompt — whole request at LC rates)
Claude Opus 4.1anthropic.claude-opus-4-1-20250805-v1:0Anthropic15.0075.00200Kpremiumexcluded (EOL Jan 8, 2027)
Claude Sonnet 4anthropic.claude-sonnet-4-20250514-v1:0Anthropic3.0015.00200KflagshipEOL (Oct 14, 2026)
Llama 4 Maverickmeta.llama4-maverick-17b-instruct-v1:0Meta0.240.971Mmidlegacy (EOL Mar 30, 2027)
Llama 4 Scoutmeta.llama4-scout-17b-instruct-v1:0Meta0.170.6610Mefficientlegacy (EOL Mar 30, 2027)
Llama 3.3 70Bmeta.llama3-3-70b-instruct-v1:0Meta0.720.72128Kmidlegacy (EOL Mar 30, 2027)
Llama 3.2 90Bmeta.llama3-2-90b-instruct-v1:0Meta0.720.72128KmidEOL (Jul 7, 2026)
Nova 2 Liteamazon.nova-2-lite-v1:0Amazon0.332.751Mmidactive
Nova 2 Pro (Preview)amazon.nova-2-pro-v1:0Amazon1.37511.001Mflagshipactive
Nova Proamazon.nova-pro-v1:0Amazon0.803.20300Kmidactive
Nova Pro (latency optimized)—Amazon1.004.00300Kmidactive
Nova Liteamazon.nova-lite-v1:0Amazon0.060.24300Kfastactive
Nova Microamazon.nova-micro-v1:0Amazon0.0350.14128Kbudgetactive
Nova Premieramazon.nova-premier-v1:0Amazon2.5012.501MreasoningEOL (2026-09-14)
Mistral Large 3mistral.mistral-large-3-675b-instructMistral0.501.50256Kflagshipactive
DeepSeek-R1deepseek.r1-v1:0DeepSeek1.355.40128Kreasoninglegacy (EOL Mar 30, 2027)
DeepSeek-V3.1deepseek.v3-v1:0DeepSeek0.581.68—midlegacy (EOL Mar 30, 2027; Sydney only)
DeepSeek V3.2deepseek.v3.2DeepSeek0.621.85164Kmidactive (US East N. Virginia/Ohio + Oregon; prefer over V3.1 for US)
gpt-oss-20bopenai.gpt-oss-20b-1:0OpenAI0.070.30128Kbudgetactive
gpt-oss-120bopenai.gpt-oss-120b-1:0OpenAI0.150.60128Kefficientactive
GPT-6 Astraopenai.gpt-6-astraOpenAI11.0055.00272Kfrontieractive (mantle in-region us-east-1/us-west-2 + runtime CRIS; Global CRIS 10.00/50.00; 1M-tier 22.00/82.50; Ultrafast 6x available)
GPT-6.1 Solopenai.gpt-6.1-solOpenAI2.2011.00272Kflagshipactive (mantle in-region us-east-1 + runtime CRIS; Global CRIS 2.00/10.00; 1M-tier 4.40/16.50; Ultrafast 6x available)
GPT-6.1 Terraopenai.gpt-6.1-terraOpenAI1.105.50272Kbalancedactive (Mantle us-east-1 or US Geo CRIS; Global 1.00/5.00; >272K In-Region/Geo 2.20/8.25, Global 2.00/7.50; Standard only)
GPT-6 Solopenai.gpt-6-solOpenAI2.2011.00272Kflagshipactive (mantle in-region us-east-1 + runtime CRIS; Global CRIS 2.00/10.00; 1M-tier 4.40/16.50)
GPT-6 Lunaopenai.gpt-6-lunaOpenAI0.110.55272Kfastactive (mantle in-region us-east-1 + runtime CRIS; Global CRIS 0.10/0.50; 1M-tier 0.22/0.825; rates and the 272K short/long boundary re-verified against the model card 2026-10-26)
GPT-5.6 Solopenai.gpt-5.6-solOpenAI4.4022.00272Kfrontieractive (mantle in-region + runtime CRIS; 1M tier 8.80/33.00)
GPT-5.6 Terraopenai.gpt-5.6-terraOpenAI2.2013.20272Kflagshipactive (mantle in-region + runtime CRIS; 1M tier 4.40/19.80)
GPT-5.6 Lunaopenai.gpt-5.6-lunaOpenAI0.221.32272Kfastactive (mantle in-region + runtime CRIS; 1M tier 0.44/1.98)
GPT-5.5openai.gpt-5.5OpenAI5.5033.00272Kfrontieractive (mantle only; no 1M tier)
GPT-5.4openai.gpt-5.4OpenAI2.7516.50272Kflagshipactive (mantle only; no 1M tier)
Gemma 4 31Bgoogle.gemma-4-31bGoogle0.140.40256Kmidactive (Mantle only)
Gemma 4 26B-A4Bgoogle.gemma-4-26b-a4bGoogle0.130.40256Kefficientactive (Mantle only)
Gemma 4 E2Bgoogle.gemma-4-e2bGoogle0.040.08128Kbudgetactive (Mantle only)
Gemma 3 4B ITgoogle.gemma-3-4b-itGoogle0.040.08128Kbudgetactive
Gemma 3 12B ITgoogle.gemma-3-12b-itGoogle0.090.29128Kbudgetactive
Gemma 3 27B ITgoogle.gemma-3-27b-itGoogle0.230.38128Kefficientactive
MiniMax M2minimax.minimax-m2MiniMax0.301.201Mmidactive
MiniMax M2.1minimax.minimax-m2.1MiniMax0.301.20196Kmidactive
MiniMax M2.5minimax.minimax-m2.5MiniMax0.301.20196Kmidactive
Jamba 1.5 Largeai21.jamba-1-5-large-v1:0AI21 Labs2.008.00—midexcluded (EOL 2026-11-26)
Jamba 1.5 Miniai21.jamba-1-5-mini-v1:0AI21 Labs0.200.40—efficientexcluded (EOL 2026-11-26)
Jurassic-2 Mid—AI21 Labs12.5012.50—legacylegacy
Jurassic-2 Ultra—AI21 Labs18.8018.80—legacylegacy
Jamba-Instruct—AI21 Labs0.500.70—midactive
Embeddings — Bedrock (per 1M input tokens, US East)

Embedding models are input-only — priced per 1M input tokens, no output charge. Use for embedding capability workloads (RAG corpora, semantic search, FAQ retrieval). A migration from an OpenAI/Azure embedding deployment lands on one of these; note the dimension must match (or the corpus must be re-embedded and any similarity threshold recalibrated).

ModelModel IDProviderInput $/1MDimensionsTierStatus
Titan Text Embeddings v2amazon.titan-embed-text-v2:0Amazon0.021024/512/256defaultactive (Active per model card; not on the pre-2026-09-07 lifecycle page as of 2026-10-26)
Titan Text Embeddings v1amazon.titan-embed-text-v1Amazon0.101536legacyactive
Cohere Embed v4cohere.embed-v4:0Cohere0.121536/1024/512/256flagshipactive
Cohere Embed English v3cohere.embed-english-v3Cohere0.101024midactive
Cohere Embed Multilingual v3cohere.embed-multilingual-v3Cohere0.101024midactive

Default target for a migrating OpenAI/Azure embedding workload: Titan Text Embeddings v2 (amazon.titan-embed-text-v2:0) — cheapest, configurable dimensions (1024 default; 512/256 for cost/latency). Choose Cohere Embed v4 when the source used a large-dimension model and matrix compatibility or multilingual quality matters. Titan v2 output dimension is configurable, so map text-embedding-3-large (3072-dim) or -small (1536-dim) to Titan 1024 and re-embed — there is no dimension-preserving swap. See references/vendored/ai/ai-openai-to-bedrock.md.

Stability AI — Image Generation (per image, US East (N. Virginia))

Active image generation models on Bedrock. Priced per image (not per token). Use for image_generation capability workloads.

ModelModel IDPrice/imageResolutionTierStatus
Stable Image Ultrastability.stable-image-ultra-v1:1$0.08up to 4MPpremiumactive
Stable Diffusion 3.5 Largestability.sd3-5-large-v1:0$0.065up to 1MPflagshipactive
Stable Image Corestability.stable-image-core-v1:1$0.04up to 1MPfastactive

Stable Image Core source: $0.04 per generated image, on-demand, from the AWS Stability AI price table on Amazon Bedrock pricing, which lists Stable Image Core for US East (N. Virginia) (verified 2026-10-25); the Stable Image Core 1.0 model card reads Active, Model EOL date N/A (verified 2026-10-26). Gemini's image-generation price for comparison: Gemini 3.1 Flash Image (Nano Banana 2) output is $30 per 1M image tokens — $0.0336 per 1K (1024×1024) image standard, $15 per 1M ($0.0168 per 1K image) batch — per Gemini API pricing (verified 2026-10-26); token-to-image equivalence with a 1MP Stable Image Core render is unverified.

Model ID source: stability.stable-image-core-v1:1 and stability.stable-image-ultra-v1:1 are the bedrock-runtime Model IDs in the Programmatic Access tables of the Stable Image Core 1.0 and Stable Image Ultra 1.0 model cards (verified 2026-10-27); both are in-Region us-west-2 only, no Geo/Global inference profile, Active, Model EOL date N/A. The earlier v1:0 suffix is not listed on any Bedrock model card or lifecycle table — do not emit it.

Image editing services (inpaint, erase, upscale, etc.) are priced at $0.03–$0.60/operation. See Bedrock pricing for full list.

Cost comparison note: DALL-E 3 (OpenAI) charges $0.04–$0.12/image depending on resolution. Google Imagen charges per character of prompt. When comparing, use per-image cost directly — do not convert Stability AI prices to per-token equivalents.

Anthropic Claude — batch & prompt cache (Standard, US East N. Virginia)

Per 1M tokens unless noted. See Bedrock pricing for full regional and tier tables.

Batch support verified 2026-09-02 against the supported Regions and models for batch inference table: Opus 4.6, Sonnet 4.6, Opus 4.5, Sonnet 4.5, Sonnet 4.5 — LC, and Haiku 4.5 are listed (via cross-region inference profiles; batch is 50% of on-demand per the pricing page, matching the rows below). Fable 5, Sonnet 5, and Opus 4.8 are NOT on that table — Sonnet 5 and Opus 4.8's batch cells below are unverified (‡): do not build a batch-discount TCO on them; price on-demand and note batch as a possible future saving pending the docs table listing them. Fable 5 / 5.1 instead carry N/A per the separate pricing-page verification below. Prompt-cache columns are unaffected (caching support is independent of batch). Batch rate vs. cross-region inference (CRIS): the confirmed rows show 50% of the N. Virginia on-demand price. Where batch is only reachable through a CRIS profile that lists above N. Virginia (e.g. Sonnet 4.6 in US East (Ohio) at ≈10% higher — see the on-demand section), the effective batch rate is 50% of that CRIS price, i.e. ≈10% above the cells here. Re-derive from the profile's on-demand rate for a region-specific quote. Do not cross-check these rows against the AWS Pricing Calculator — as of Sep 2026 the calculator carries no batch metered IDs for Opus 4.6 / Sonnet 4.6 and collapses other batch/cache SKUs (known calculator defect, not a pricing-page signal). The pricing page and the docs table above are the sources of truth.

ModelBatch inBatch out5m cache write1h cache writeCache read
Claude Fable 5N/AN/A12.5020.001.00
Claude Fable 5.1N/AN/A12.5020.000.25
Claude Sonnet 51.00 ‡5.00 ‡2.504.000.20
Claude Sonnet 5.5 (Global)N/AN/A2.504.000.10
Claude Sonnet 5.5 (US Geo)N/AN/A2.754.400.11
Claude Haiku 5.5 (Global)N/AN/A0.1250.200.01
Claude Haiku 5.5 (Global) — LCN/AN/A0.6251.000.05
Claude Haiku 5.5 (US Geo)N/AN/A0.13750.220.011
Claude Haiku 5.5 (US Geo) — LCN/AN/A0.68751.100.055
Claude Opus 5.5 (Global)N/AN/A5.008.000.20
Claude Opus 5.5 (commercial Geo/Mantle/London runtime)N/AN/A5.508.800.22
Claude Opus 5.5 (GovCloud)N/AN/A6.009.600.24
Claude Opus 4.82.50 ‡12.50 ‡6.2510.000.50
Claude Sonnet 4.6 (+ LC)1.507.503.756.000.30
Claude Opus 4.6 (+ LC)2.5012.506.2510.000.50
Claude Opus 4.52.5012.506.2510.000.50
Claude Haiku 4.50.502.501.252.000.10
Claude Sonnet 4.51.507.503.756.000.30
Claude Sonnet 4.5 — LC3.0011.257.5012.000.60

Batch: the Bedrock pricing page lists N/A for Claude Fable 5 and Fable 5.1 in both the Global and the Geo / In-region Anthropic tables (read 2026-09-03). Anthropic's first-party API offers a 50% batch discount on these models; Bedrock does not list one — do not assume a batch rate for Fable-class models.

‡ Not listed on the batch-supported models table as of 2026-09-02 — rate is the standard 50%-of-on-demand projection, not a confirmed SKU. Mark these batch cells _unverified_ in estimate output; the unverified gate in estimate-ai.md (§ Pricing source caveat) treats any _unverified_ row as blocking for a quoted figure — resolve from the Bedrock pricing page first.

AI21 Labs

On-demand, US East (N. Virginia) per Amazon Bedrock pricing. Prices per 1M input / output tokens.

ModelInput $/1MOutput $/1M
Jamba 1.5 Large2.008.00
Jamba 1.5 Mini0.200.40
Jurassic-2 Mid12.5012.50
Jurassic-2 Ultra18.8018.80
Jamba-Instruct0.500.70

Quick-reference rows use — for model ID and context; resolve in the Bedrock console or AWS model documentation.

Mistral AI

Per Amazon Bedrock pricing (Mistral AI). Priority tier ≈ +75% vs Standard; Flex ≈ −50% vs Standard on the same page.

US East (Ohio) — Pixtral (on-demand + batch header from page)
ModelInput $/1MOutput $/1MBatch inBatch out
Pixtral Large (25.02)2.006.00N/AN/A
On-demand — US East (N. Virginia), US East (Ohio), US West (Oregon)

Prices per 1M input / output tokens.

ModelInput $/1MOutput $/1M
Devstral 2 123B0.402.00
Magistral Small 1.20.501.50
Voxtral Mini 1.00.040.04
Voxtral Small 1.00.100.30
Ministral 3B 3.00.100.10
Ministral 8B 3.00.150.15
Ministral 14B 3.00.200.20
Mistral Large 30.501.50

Rates differ in Asia Pacific (Mumbai), São Paulo, Tokyo, Europe (Ireland/Milan/London), Sydney, Jakarta, Frankfurt, Stockholm (e.g. Mistral Large 3 Mumbai $0.59 / $1.76). Devstral 2 123B appears in Jakarta / Frankfurt / Stockholm at $0.48 / $2.40 on the same page.

DeepSeek (Amazon Bedrock)

Per Amazon Bedrock pricing (DeepSeek).

US East (Ohio) — Standard tier

Note: DeepSeek-V3.1 is no longer listed for US East regions on the Bedrock pricing page as of May 2026. Use DeepSeek-V3.2 for US East deployments. DeepSeek-V3.1 remains available in Asia Pacific (Sydney).

ModelInput $/1MOutput $/1M
DeepSeek-R11.355.40
US East (N. Virginia), US East (Ohio), US West (Oregon)
ModelInput $/1MOutput $/1M
DeepSeek v3.20.621.85
Other regions (examples on same page)
  • Asia Pacific (Mumbai), São Paulo, Jakarta, Tokyo, Stockholm: DeepSeek v3.2 $0.74 / $2.22 per 1M.

  • Asia Pacific (Sydney): DeepSeek v3.1 $0.5974 / $1.7304; v3.2 $0.6386 / $1.9055 (and Priority / Flex tiers listed separately on the page).

OpenAI on Bedrock (GPT-6, GPT-5.6, and gpt-oss)

See shared/openai-on-bedrock.md for model IDs, endpoint paths, regions, quotas, and caching rules. Bedrock in-region is priced at parity with OpenAI's data residency tier — exactly 1.10x OpenAI's standard list price — so a same-model migration costs about 10% MORE, not the same. Do not describe it as cost-neutral.

GPT-6 family — short context (≤272K)

GPT-6 Astra, GPT-6 Sol, GPT-6 Luna, and GPT-6.1 Sol are priced the same In-Region/Geo-CRIS vs. Global-CRIS way as GPT-5.6: In-Region and Geo-CRIS carry the ~10% data-residency premium over OpenAI's standard rate, while Global CRIS is published at OpenAI's standard list price (cost parity). Figures below are in · cache-write · cache-read · out, per 1M tokens.

ModelIn-Region/Geo-CRIS (in · cache-write · cache-read · out)Global CRIS (in · cache-write · cache-read · out)
GPT-6 Astra11.00 · 13.75 · 1.10 · 55.0010.00 · 12.50 · 1.00 · 50.00
GPT-6 Sol2.20 · 2.75 · 0.22 · 11.002.00 · 2.50 · 0.20 · 10.00
GPT-6 Luna0.11 · 0.1375 · 0.011 · 0.550.10 · 0.125 · 0.01 · 0.50
GPT-6.1 Sol2.20 · 2.75 · 0.11 · 11.002.00 · 2.50 · 0.10 · 10.00

GPT-6.1 Sol's cache-read rate is deeper (0.05x vs the other three models' 0.10x) — this is the one real pricing difference from GPT-6 Sol beyond capability.

GPT-6 family — long context (>272K; 1.05M context window)

Full request — input, cache, and output — is repriced at 2x input/cache and 1.5x output above 272K input tokens.

ModelIn-Region/Geo-CRIS (in · cache-write · cache-read · out)Global CRIS (in · cache-write · cache-read · out)
GPT-6 Astra22.00 · 27.50 · 2.20 · 82.5020.00 · 25.00 · 2.00 · 75.00
GPT-6 Sol4.40 · 5.50 · 0.44 · 16.504.00 · 5.00 · 0.40 · 15.00
GPT-6 Luna0.22 · 0.275 · 0.022 · 0.8250.20 · 0.25 · 0.02 · 0.75
GPT-6.1 Sol4.40 · 5.50 · 0.22 · 16.504.00 · 5.00 · 0.20 · 15.00

GPT-6 Astra and GPT-6.1 Sol also support a 6x-Standard Ultrafast service tier (service_tier: "ultrafast"), confirmed on both model cards' "Service Tiers" sections; GPT-6 Sol, GPT-6 Luna, and GPT-6.1 Terra are Standard-only. None of the five GPT-6 models support Priority, Flex, or Reserved. See shared/openai-on-bedrock.md for the full breakdown, including per-model Ultrafast availability by region.

Proprietary GPT models — short context (272K), in-region

Regions (mantle): us-east-1 / us-east-2 for all five; us-west-2 additionally carries Terra, Luna and GPT-5.4; AWS GovCloud us-gov-west-1 / us-gov-east-1 carry Terra and Luna, us-gov-west-1 also GPT-5.4 (at its own rate below). Rates reflect the July 30, 2026 reduction (Luna −80%, Terra −20%) and the Aug 21, 2026 Sol reduction (−20% input / −33% output, promotional through at least Nov 21, 2026).

ModelInput $/1MOutput $/1MCache write $/1MCache read $/1M
GPT-5.6 Sol4.4022.005.500.44
GPT-5.6 Terra2.2013.202.750.22
GPT-5.6 Luna0.221.320.2750.022
GPT-5.55.5033.00—0.55
GPT-5.42.7516.50—0.275
Long context (1M) — GPT-5.6 only, 2.0x input / 1.5x output
ModelInput $/1MOutput $/1M
GPT-5.6 Sol8.8033.00
GPT-5.6 Terra4.4019.80
GPT-5.6 Luna0.441.98

A workload above 272K context must be priced at the long-context tier. GPT-5.5 and GPT-5.4 have no such tier, so their usable window is 272K. Global CRIS is published at OpenAI's standard list price (cost parity, GPT-5.6 only — see openai-on-bedrock.md). GovCloud GPT-5.4 is 3.30 / 19.80.

One source conflict. These models are absent from the AWS Price List API entirely: querying AmazonBedrock returns only gpt-oss and GPT OSS Safeguard, and filtering on GPT-5 or a gpt-5 usage type returns zero rows (price-list publication 2026-08-04). An empty price-list result is not evidence the model is unavailable. (An earlier revision also flagged the AWS News Blog's Luna 0.20 / 1.20 as conflicting; it is the Global CRIS rate, not an error.)

Prompt caching (GPT-5.6 only): cached input read at a 90% discount, cache write at 1.25x uncached input, minimum 1,024-token prefix, up to 4 breakpoints, ≥30-minute retention. Cached input is exempt from the input-TPM quota. GPT-5.5 and GPT-5.4 do not list prompt caching support.

Open-weight gpt-oss
ModelRegionInput $/1MOutput $/1M
gpt-oss-20bUS East (Ohio)0.070.30
gpt-oss-120bUS East (Ohio)0.150.60
gpt-oss-20bAsia Pacific (Sydney)0.07210.3090
gpt-oss-120bAsia Pacific (Sydney)0.15450.6180

The Bedrock page also lists Flex, Priority, Batch, GPT OSS Safeguard, and model customization pricing for other regions.

Meta Llama (Amazon Bedrock)

Per Amazon Bedrock pricing (Meta). Prices per 1M input / output tokens unless noted.

Llama 4 — US East (Ohio), on-demand and batch
ModelOn-demand inOn-demand outBatch inBatch out
Llama 4 Maverick 17B0.240.970.120.485
Llama 4 Scout 17B0.170.660.0850.33
Llama 3.3 — US East (Ohio), on-demand and batch
ModelOn-demand inOn-demand outBatch inBatch out
Llama 3.3 Instruct (70B)0.720.720.360.36
Llama 3.2 — US East (Ohio), on-demand and batch

Lifecycle note: All Llama 3.2 Instruct models reached EOL on Jul 7, 2026 and are no longer available for inference on Bedrock. Do not select for any migrations. Prefer Nova Micro / Lite or Claude Haiku 4.5 (Llama 4 Scout / Maverick are now Legacy — EOL Mar 30, 2027). See vendored/ai/ai-model-lifecycle.md.

ModelOn-demand inOn-demand outBatch inBatch out
Llama 3.2 Instruct (1B)0.100.10N/AN/A
Llama 3.2 Instruct (3B)0.150.15N/AN/A
Llama 3.2 Instruct (11B)0.160.16N/AN/A
Llama 3.2 Instruct (90B)0.720.72N/AN/A
Llama 3.2 — customization & provisioned throughput (US West Oregon)

Fine-tuning (per 1M tokens trained / month storage / no-commit PT per model unit-hour):

ModelTrain 1M tokensStore / monthInfer / unit-hr (no commit)
Llama 3.2 Instruct (1B)$0.50$1.95$23.00
Llama 3.2 Instruct (3B)$1.10$1.95$23.00
Llama 3.2 Instruct (11B)$3.50$1.95$23.00
Llama 3.2 Instruct (90B)$7.90$1.95$30.00

Provisioned throughput ($/hour per model unit):

ModelNo commit1-mo commit6-mo commit
Llama 3.2 Instruct (1B)$23.00$20.30$12.54
Llama 3.2 Instruct (3B)$23.00$20.30$12.54
Llama 3.2 Instruct (11B)$23.00$20.30$12.54
Llama 3.2 Instruct (90B)$30.00$26.48$16.35
Llama 3.1 — US East (Ohio), on-demand and batch

Lifecycle note: Llama 3.1 405B Instruct reached EOL on Jul 7, 2026 and is no longer available for inference on Bedrock. Do not select for any migrations. Prefer Nova Pro or Claude Sonnet 5 (Llama 4 Maverick is now Legacy — EOL Mar 30, 2027). See vendored/ai/ai-model-lifecycle.md.

ModelOn-demand inOn-demand outBatch inBatch out
Llama 3.1 Instruct (8B)0.220.220.110.11
Llama 3.1 Instruct (70B)0.720.720.360.36
Llama 3.1 Instruct (405B)2.402.401.201.20
Llama 3.1 Instruct (70B) (latency optimized inf.)0.900.90N/AN/A
Llama 3.1 Instruct (405B) (latency optimized inf.)3.003.00N/AN/A
Llama 3.1 — customization & provisioned throughput (US West Oregon)
ModelTrain 1M tokensStore / monthInfer / unit-hr (no commit)
Llama 3.1 Instruct (8B)$1.49$1.95$24.00
Llama 3.1 Instruct (70B)$7.99$1.95$24.00
ModelNo commit1-mo commit6-mo commit
Llama 3.1 Instruct (8B)$24.00$21.18$13.08
Llama 3.1 Instruct (70B)$24.00$21.18$13.08
Llama 3 — US East (N. Virginia), on-demand
ModelInput $/1MOutput $/1M
Llama 3 Instruct (8B)0.300.60
Llama 3 Instruct (70B)2.653.50
Llama 2 — US East (N. Virginia) and US West (Oregon), on-demand
ModelInput $/1MOutput $/1M
Llama 2 Chat (13B)0.751.00
Llama 2 Chat (70B)1.952.56
Llama 2 — customization & provisioned throughput

Fine-tuning: Llama 2 Pretrained (13B) $1.49 per 1M tokens trained, $1.95/month storage, $23.50/unit-hr no-commit infer; (70B) $7.99 / $1.95 / $23.50.

Provisioned throughput (per model unit-hour): 13B and 70B — $21.18 (1-mo commit), $13.08 (6-mo commit). Pretrained Llama 2 is provisioned throughput only after customization per AWS.

Amazon Nova

All figures from Amazon Bedrock pricing (Amazon Nova sections). Nova pricing depends on inference deployment (e.g. Global cross-region vs Geo cross-region and in-region), tier (Standard, Priority, Flex, Batch), modality (text / image / video / audio), and AWS Region. The quick-reference table above uses Geo cross-region inference and in-region, Standard tier, US East (Ohio), text + image + video rates where a single input price applies to all three. Confirm the page before estimates.

Cache read (Nova): AWS states cache read input tokens are 75% below the on-demand input price for the applicable tier/modality.

US East (Ohio) — Standard tier, text + image + video (Geo cross-region inference and in-region)

Per 1M input / output tokens unless noted.

ModelInput $/1MOutput $/1M
Amazon Nova 2 Lite0.332.75
Amazon Nova Micro0.0350.14
Amazon Nova Lite0.060.24
Amazon Nova Pro0.803.20
Amazon Nova Pro (latency optimized inf.)1.004.00
Amazon Nova Premier2.5012.50
US East (Ohio) — Standard tier, Global cross-region inference (text + image + video)
ModelInput $/1MOutput $/1M
Amazon Nova 2 Lite0.302.50
US East (Ohio) — Standard tier, text / image / video / audio (Geo cross-region and in-region)

Per 1M tokens. Nova 2 Omni and Nova 2 Pro are Preview. Image column is output image pricing where listed.

ModelText inImage inVideo inAudio inText outImage out
Amazon Nova 2 Omni (Preview)0.300.300.301.102.8044.00
Amazon Nova 2 Pro (Preview)1.3751.3751.3751.37511.00N/A

Global cross-region inference (Ohio), Standard uses different multimodal numbers on the same page — e.g. Nova 2 Omni (Preview) audio in $1.00, text out $2.50, image out $40.00 (text/image/video in $0.30 each). Use the Bedrock pricing page for the deployment you select.

US East (Ohio) — Nova 2 Lite by tier (text + image + video)
Global cross-region inference
TierInput $/1MOutput $/1M
Standard0.302.50
Priority0.5254.375
Flex0.151.25
Batch0.151.25
Geo cross-region inference and in-region
TierInput $/1MOutput $/1M
Standard0.332.75
Priority0.57754.8125
Flex0.1651.375
Batch0.15951.342
US East (Ohio) — Batch tier (text + image + video), selected models
ModelInput $/1MOutput $/1M
Amazon Nova 2 Lite0.15951.342
Amazon Nova Micro0.01750.07
Amazon Nova Lite0.030.12
Amazon Nova Pro0.401.60
Amazon Nova Premier1.256.25
On-demand inference (listed rates, cache read column)
ModelInput $/1MCache read $/1MOutput $/1M
Amazon Nova 2.0 LiteN/AN/AN/A
Amazon Nova Micro0.035N/A0.14
Amazon Nova Lite0.06N/A0.24
Amazon Nova Pro0.80N/A3.20
Built-in tools — Web grounding (US East Ohio)
ModelPrice
Amazon Nova 2 Omni (Preview)$30.00 per 1K requests
Amazon Nova 2 Pro (Preview)$30.00 per 1K requests
Creative — US East (N. Virginia)

Lifecycle note: Nova Canvas v1 and Nova Reel v1 are past EOL (2026-09-30) and listed under Removed in ai-model-lifecycle.md. Inference requests fail. Do not list them in recommendation or comparison tables. Rates below are historical, retained so users who were on them can see what they paid. See vendored/ai/ai-model-lifecycle.md.

Amazon Nova Canvas (on-demand, per image): up to 1024×1024 — Standard $0.04, Premium $0.06; up to 2048×2048 — Standard $0.06, Premium $0.08.

Model customization (Nova Canvas): $0.005 per image seen; $1.95/month per custom model stored; provisioned inference per model unit per hour (no commit / 1-mo / 6-mo) $60.50 / $55.00 / $30.25.

Amazon Nova Reel (video): 720p, 24 fps — $0.08 per second of video generated.

Speech — US East (N. Virginia)

Lifecycle note: Nova Sonic v1 reached EOL on 2026-09-14 and its requests now fail. Rates are retained only to explain the migration to Nova 2 Sonic. See vendored/ai/ai-model-lifecycle.md.

Per 1M tokens.

ModelModalityInput $/1MOutput $/1MStatus
Amazon Nova SonicSpeech3.4013.60EOL (2026-09-14)
Amazon Nova SonicText0.060.24EOL (2026-09-14)
Amazon Nova 2 SonicSpeech3.0012.00active
Amazon Nova 2 SonicText0.332.75active
Multimodal embeddings — US East (N. Virginia)
OfferingText $/1MStd image / doc image / video sec / audio sec
Amazon Nova Multimodal Embeddings (On-demand)0.135$0.00006 / $0.0006 / $0.0007 / $0.00014 per unit
Amazon Nova Multimodal Embeddings (Batch)0.0675$0.00003 / $0.00048 / $0.00056 / $0.000112

On-demand inference for custom Nova models matches base Nova inference pricing per AWS.


Requirements and compatibility

Written for: Claude Code

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Names Claude Code tools, Needs Python

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
AWS
Publisher
AWS (Official)
Source
aws/agent-toolkit-for-aws · plugins/aws-startup-advisor/skills/agent-advisor · commit 0a218f8
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • NOTICE (added by AutoGineer from NOTICE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by AWS or AWS.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download agent-advisor.zip