LLMEOL CodeAP Studio

Amazon Nova & Titan Foundation Models Deprecation, Shutdown Dates & Migration Guide

Runs locally in your browser — 0 bytes uploaded Synced 2026-11-12 UTC · 15 variants · 1 ecosystems

Track confirmed UTC deprecation and shutdown dates for Amazon Nova & Titan Foundation Models (Amazon) across AWS Bedrock. Preview amazon.nova-sonic-v1:0 → amazon.nova-pro-v1:0 upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.

Tracked Variants 15
Earliest Upcoming EOL No EOL
Recommended Upgrade amazon.nova-pro-v1:0
Ecosystems Covered AWS Bedrock

1. Quick .env & SDK Snippet Replacement Matcher

Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.

2 of 2 configured models need migration
Full .env Auditor → Compare amazon.nova-pro-v1:0 Cost in DevToken →

Replacement Diff Preview (amazon.nova-sonic-v1:0 → amazon.nova-pro-v1:0)

# BEDROCK_MODEL_ID: amazon.nova-sonic-v1:0 -> amazon.nova-pro-v1:0 [RETIRED · EOL 2026-09-14]
- BEDROCK_MODEL_ID="amazon.nova-sonic-v1:0"
+ BEDROCK_MODEL_ID="amazon.nova-pro-v1:0"

# model: amazon.nova-sonic-v1:0 -> amazon.nova-pro-v1:0 [RETIRED · EOL 2026-09-14]
- model: bedrock/amazon.nova-sonic-v1:0
+ model: bedrock/amazon.nova-pro-v1:0

2. Cross-Ecosystem Amazon Nova & Titan Foundation Models Lifecycle Matrix (15)

Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.

Amazon Nova & Titan Foundation Models lifecycle status, UTC shutdown dates, and replacement models across AWS Bedrock
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
amazon.nova-canvas-v1:0 AWS Bedrock(Amazon) RETIRED 2026-09-3043d ago EOLDep: 2026-03-30ap-northeast-1, eu-west-1, us-east-1
—Audit →
 Docs ↗
amazon.nova-reel-v1:0 AWS Bedrock(Amazon) RETIRED 2026-09-3043d ago EOLDep: 2026-03-30ap-northeast-1, eu-west-1, us-east-1
—Audit →
 Docs ↗
amazon.nova-reel-v1:1 AWS Bedrock(Amazon) RETIRED 2026-09-3043d ago EOLDep: 2026-03-30us-east-1
—Audit →
 Docs ↗
amazon.nova-sonic-v1:0 AWS Bedrock(Amazon) RETIRED 2026-09-1459d ago EOLDep: 2026-03-13ap-northeast-1, eu-north-1, us-east-1
—Audit →
 Docs ↗
amazon.nova-2-5-sonic AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-2-lite-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-2-multimodal-embeddings-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-2-sonic-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-lite-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-micro-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.nova-pro-v1:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.titan-embed-g1-text-02 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.titan-embed-image-v1 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.titan-embed-text-v1 AWS Bedrock(Amazon) ACTIVE No EOL Active — —
amazon.titan-embed-text-v2:0 AWS Bedrock(Amazon) ACTIVE No EOL Active — —

AWS Bedrock regional scope applies across 4 tracked regions (ap-northeast-1, eu-north-1, eu-west-1, us-east-1); verify regional inference prefixes (us., eu., apac., global.) before cutover.

3. Production Migration Checklist (amazon.nova-sonic-v1:0 → amazon.nova-pro-v1:0)

Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:

  1. Inventory pinned model IDs: Search repositories and deployment manifests for BEDROCK_MODEL_ID, bedrock/ LiteLLM routes, and dated snapshot strings in the Amazon Nova & Titan Foundation Models family (0 deprecated, 4 retired, 11 active variants tracked).
  2. Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against amazon.nova-pro-v1:0, then compare input, output, and cached token rates in DevToken.
  3. Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated Amazon Nova & Titan Foundation Models identifiers cannot re-enter production.

Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:

5. Amazon Nova & Titan Foundation Models Deprecation & Upgrade FAQ

Is Amazon Nova & Titan Foundation Models deprecated or retired across AWS Bedrock?

LLMEOL tracks 15 Amazon Nova & Titan Foundation Models variants across AWS Bedrock: 0 deprecated with scheduled shutdowns, 4 retired past their UTC EOL date, and 11 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.

What is the recommended replacement model when migrating off amazon.nova-sonic-v1:0?

The primary recommended upgrade target for amazon.nova-sonic-v1:0 is amazon.nova-pro-v1:0. Always test prompt formatting, max output tokens, and tool schemas on amazon.nova-pro-v1:0, and compare token pricing in DevToken before switching production traffic.

How can I replace amazon.nova-sonic-v1:0 in .env and LiteLLM configs safely?

Paste your BEDROCK_MODEL_ID assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.