amazon-nova-reel
Amazon Nova Reel production
Treat Nova Reel as an asynchronous production service, not a synchronous clip function. Plan the shots, validate every input, obtain an exact approval, submit once with an idempotency token, persist the invocation ARN, and promote only validated S3 artifacts.
All volatile facts in this skill were verified against first-party AWS sources on 2026-07-10. Recheck model access, Region, price, quota, and lifecycle immediately before a paid run.
Establish the current contract
Do not select Nova Reel as a new default. AWS's Bedrock lifecycle table marks both published Reel versions Legacy as of 2026-03-30, with EOL 2026-09-30:
| Model | Region(s) | Current use |
|---|---|---|
amazon.nova-reel-v1:1 |
us-east-1 |
Only an already-authorized, still-active workload that needs Reel 1.1 capabilities and has a funded exit plan |
amazon.nova-reel-v1:0 |
us-east-1, eu-west-1, ap-northeast-1 |
Existing six-second legacy workloads only; do not migrate new work onto it |
New customers cannot use Legacy models, existing customers may lose access after 15 days of inactivity, and new Provisioned Throughput cannot be created. On or soon after EOL, calls fail unless the customer has a private continued-access arrangement. Migration is not automatic. AWS's table does not identify an active Nova Reel successor, so do not invent one: for work that must operate past EOL, select another currently active provider unless AWS publishes a successor or the account team confirms a private arrangement.
Where the account has confirmed Reel 1.1 access and the delivery can finish before EOL, Reel 1.1 supports: