AWS retires Nova Reel video model on Bedrock

Amazon.nova-reel-v1:0 hits its published Sept. 30, 2026, end-of-life date in Virginia, Ireland and Tokyo

Amazon Web Services on Wednesday reaches the published end-of-life date for Amazon Nova Reel on Amazon Bedrock. The model ID on the card is amazon.nova-reel-v1:0. The cutoff listed there is Sept. 30, 2026.

AWS put the same date on the legacy lifecycle table. Reel 1.0 is marked Legacy in US East (N. Virginia), Europe (Ireland) and Asia Pacific (Tokyo). In-Region inference. Geo and global routing are not supported on that card.

The policy language does not leave much room. After the EOL date, AWS says a model “will be marked EOL in the console.” Then: “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.”

Code does not migrate itself. “Migration will not happen automatically.” “You will need to migrate to the latest model by updating your application code before the EOL date.”

Reel launched Dec. 3, 2024, with the first Nova family. Models that arrived on Bedrock before Sept. 7, 2026, stay listed for at least 12 months before end of life. Reel cleared that mark. It entered Legacy on March 30, 2026. AWS required at least six months in that state. The public extended-access column for this ID is a dash.

Legacy already shut the front door. “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 barred. Fine-tuning was never on the Reel spec sheet. The Nova video guide lists Fine-tuning: No. Provisioned throughput: No.

The card still describes the job. “Nova Reel is Amazon’s video generation model that creates short videos from text and image prompts with camera motion controls.”

That work ran asynchronously. The model card lists StartAsyncInvoke among the supported APIs. Synchronous Invoke is listed as no on the generation table. Output landed in an Amazon S3 bucket the caller named. AWS documentation puts a 6-second clip at about 90 seconds of wait time. A two-minute job is listed at about 14 to 17 minutes.

Resolution was 1280 by 720. Frame rate was 24. Duration came in six-second increments. English prompts. Text-to-video. Text and image-to-video. PNG and JPEG inputs. Images pulled from S3 could not exceed 25 MB. Input images that failed the 1280-by-720 check were treated as validation errors.

Prompt length sat in a tight box. Text-to-video: 512 characters. Multi-shot automated: 4,000 characters. Multi-shot manual: 512 characters per shot.

Reel 1.0 and Reel 1.1 are not the same ID. AWS says Amazon Nova Reel 1.0 ran in N. Virginia, Ireland and Tokyo. Amazon Nova Reel 1.1 ran only in US East (N. Virginia). “To generate videos longer than six seconds, you must use amazon.nova-reel-v1:1 as the model ID.” The July 16, 2025, service card draws the same line. Reel 1.0: videos of up to 6 seconds from a text prompt, or from a reference image plus text. Longer runs belonged to 1.1.

The lifecycle table still puts both IDs on Wednesday’s calendar. amazon.nova-reel-v1:1 is listed Legacy as of March 30, 2026, with an EOL date of Sept. 30, 2026, in us-east-1. Public extended access for that row is also blank.

The v1:0 model card does not name a successor ID. Bedrock recommends the bedrock-runtime endpoint for new applications. An example runtime URL in N. Virginia is here. Pricing is on the Bedrock price page, not the card. Quotas sit on the quota page. License text is on the Bedrock third-party models legal page.

Anyone still calling amazon.nova-reel-v1:0 has a short list. Check the account. Check the Region. Call ListFoundationModels or GetFoundationModel and read the lifecycle field. A private arrangement is the exception AWS wrote down. Otherwise the model ID has to leave the StartAsyncInvoke path. The docs do not promise a grace day past “on, or soon after.”