Amazon introduced Nova Micro, Lite and Pro on 3 December 2024 in Amazon Bedrock. It also announced Canvas and Reel as separate image and video generation offerings. Micro was described as text-only; Lite and Pro as multimodal for text, image and video inputs. Treating the whole Nova name as one generic multimodal product would produce misleading search filters and the wrong API expectations.
Select by workload
A text-only classification and extraction queue can consider Micro. Document-image analysis may require Lite or Pro. For video input, inspect preprocessing, frame sampling and supported container constraints instead of assuming a continuous media stream. Image/video generation belongs to separate model IDs and to editorial owners AI 03–04.
Bedrock is a deployment layer
AWS exposes foundation models through Bedrock abstractions, so inference profiles, permission policies and model entitlement are part of the integration. The model ID configured for a Bedrock invocation can differ from a provider’s own API ID. Record AWS account/region and the selected inference profile separately from the canonical Nova release.
Residency versus routing
AWS documentation distinguishes geography-bounded cross-Region profiles from global routing. Choosing an EU-labeled geography-bound profile is materially different from asking for processing only in a single specific AWS Region. Data may traverse permitted regions within the geography. Legal teams should evaluate the actual service terms, logging and abuse-detection handling.
What good tests include
Use an identical corpus with grounded answers, record task-completion and token usage, and test permission-denied as well as limit-exceeded states. A launch claim of price/performance is a vendor claim, not an independent benchmark. Subscription or usage charges require a dated AI 10 snapshot.
What to verify before adopting this model or method
Use the exact release ID and API endpoint; confirm your geographic processing location, entitlement tier, model lifecycle, feature flags, context and output limits from the provider console. Run a reproducible evaluation on your own data and retain human oversight for consequential actions. Where a specification, price, commercial license or entitlement is not verified for your deployment, this article deliberately leaves it unasserted instead of filling a plausible number.
Sources & Further Reading
- aws.amazon.com — documentation/reference (supplier-provided reference; not independently checked in this pass)
- docs.aws.amazon.com — documentation/reference (supplier-provided reference; not independently checked in this pass)
Source documentation establishes vendor-published facts, not independently measured model quality, tenant access, contractual rights or current prices. Use a dated pricing ledger and an account-specific entitlement check for deployment decisions.