Amazon Web Services on Wednesday reaches the documented end-of-life date for Amazon Nova Canvas on Amazon Bedrock. The model ID is amazon.nova-canvas-v1:0. The model card lists Sept. 30, 2026.
That date is not a forecast. It is the date AWS printed on the card and in the legacy lifecycle table. Canvas is marked Legacy in the three Regions where it ran: US East (N. Virginia), Europe (Ireland) and Asia Pacific (Tokyo). In-Region inference only. No geo inference. No global cross-Region path.
What happens next is written in the same policy. After the EOL date, AWS says, a model “will be marked EOL in the console.” Then this: “On, or soon after the EOL date, the model is no longer available for use in all AWS Regions and requests made to this version will fail, unless there is a private arrangement between you and the provider for continued access.”
No automatic cutover. AWS is blunt about that. “Migration will not happen automatically.” “You will need to migrate to the latest model by updating your application code before the EOL date.”
Canvas launched Dec. 3, 2024, during the first Nova wave. For models that arrived on Bedrock before Sept. 7, 2026, AWS says a model “will remain on Amazon Bedrock for at least 12 months before the EOL date.” Canvas cleared that floor. It moved to Legacy on March 30, 2026. Policy required at least six months in that state. The public extended-access column for this ID is a dash. No extra public window is listed.
Legacy already narrowed the on-ramp. “New customers can’t use Legacy models and existing customers may lose access to Legacy models after 15 days of inactivity.” New Provisioned Throughput was off the table. After a foundation model enters Legacy, AWS also says new fine-tuning jobs on that model cannot be created.
The work the ID was built to do did not change on paper. The model card still reads: “Nova Canvas is Amazon’s image generation model that creates studio-quality images from text and image prompts with built-in controls for watermarking and content moderation.”
Developers hit it through the bedrock-runtime endpoint. AWS also lists bedrock-mantle. Invoke carried most image jobs. Prompts were English. Input images were PNG or JPEG. The prompt cap was 1,024 characters across positive and negative fields. Generation output topped out at 4.19 million pixels — 2048 by 2048, or 2816 by 1536. Editing jobs had a separate box: no more than 4,096 pixels on the long side, aspect ratio between 1:4 and 4:1, same pixel ceiling.
The July 2, 2025, service card is the release AWS still points to for the feature set. Virtual try-on. Style presets. Inpainting. Outpainting. Background removal. Hex-code color guidance. Variation from one to five reference images. An invisible watermark on generated frames, with a detection check for Nova output. Subject consistency was documented through fine-tuning on reference images. Provisioned Throughput was listed as unavailable on the generation spec sheet even before Legacy rules blocked new capacity.
The card does not name a replacement model ID. Teams still calling amazon.nova-canvas-v1:0 have to pick the next Active model themselves and change the code.
The same lifecycle table puts Amazon Nova Reel on the same calendar. amazon.nova-reel-v1:0 shares the March 30, 2026, Legacy date and the Sept. 30, 2026, EOL date in ap-northeast-1, eu-west-1 and us-east-1. amazon.nova-reel-v1:1 is listed for us-east-1 with the same two dates.
Pricing is not on the model card. AWS sends that to the Bedrock pricing page. Quotas sit on the Bedrock quota page. License language is on the Bedrock third-party models legal page.
For anyone who still has Canvas wired into production, the checklist is short. Confirm the account still has access. Confirm the Region. Call ListFoundationModels or GetFoundationModel and read the lifecycle field. If the job must keep running after Wednesday, that requires a private arrangement AWS itself describes as the exception, not the default. Otherwise the model ID has to come out of the request path.
The documentation does not promise a grace day beyond “on, or soon after.” It promises failed requests once the version is gone.
No tracking, no middleman. Follow by RSS (nothing is collected) — or add your email to our self-hosted list.
RSS feed →