MODEL PROFILE · Amazon
Amazon Nova Canvas v1:0
AWS lists September 30, 2026 as this image model’s end-of-life date. Identify the exact Bedrock integration before selecting an image-generation replacement.
Source reviewed: · Image model · legacy
Provider documentation summary. No hands-on results or independent ranking are claimed.
Documented facts
The following fields come from the official provider source, reviewed on the date above.
- Exact identity
- amazon.nova-canvas-v1:0 on Amazon Bedrock.
- Inputs and output
- Text and image inputs; image output. The card does not support audio or video inputs.
- Documented API
- Invoke through bedrock-runtime; not Converse, Chat Completions or Responses.
- Lifecycle
- Launched December 3, 2024; card labels it Legacy with EOL September 30, 2026.
- Listed regions
- us-east-1, eu-west-1 and ap-northeast-1, each carrying the same EOL label.
- Pricing and license
- The card links Bedrock pricing and AWS terms. This review establishes no current per-image rate or downloadable-weight license.
A retirement schedule, not an observed outage
AWS lists March 30, 2026 as the legacy date. Its policy says requests fail on or soon after EOL unless there is a private continued-access arrangement. Migration does not happen automatically. No exact cutoff time is stated. We made no inference request, so we cannot report whether a particular account still receives output today. AWS legacy lifecycle policy and model table.
The practical decision
Start with the job Canvas served. A product-background edit and a fresh illustration are different requirements even when both produce an image. Keep a small set of your existing inputs and accepted outputs, and write down what must remain unchanged: a label, silhouette, color, layout or subject identity. Choose a replacement whose documented inputs support that same task. A convincing first sample cannot establish that the integration will handle the rest of your workload.
What to record in your own comparison
- Read the literal model identifier and region from your configuration; a friendly model label can hide the version. Preserve the request schema and original references.
- For an editing workflow, inspect the unchanged product as closely as the changed background. Check lettering, edges and geometry at the delivery size. For text-to-image, use the same content and layout requirements.
- Confirm replacement access, output dimensions, response format and billing units before changing application routing. Compare saved outputs in the editor; do not mistake a different API contract for a drop-in replacement.
- Keep a documented fallback for failed requests and validate it on your own acceptance criteria. This profile does not certify any alternative or perform a migration.
Limitations and unknowns
Documentation research only; no generated examples, independent quality findings or endpoint availability test. Maximum dimensions, editing-mode limits, current charges and open-weight access are not established here. Do not import specifications from Nova Reel: it is a separate video model. A model card remaining online is not proof that requests still work.
Compare your saved results
Use the DualView editor to inspect files you already have. The accepted-output calculator uses your own rates and counts. Neither link runs a model or purchases generation.
Related reporting
- Qwen Image 2.1: a separately documented image-model alternative to evaluate
- Hy Image 3.5 Preview: image editing and access limitations