# Amazon Nova API

## Kurzbeschreibung
**Amazon Nova** is Amazon's own family of foundation models for text, image/video understanding, document analysis, agents, tool use, and speech. 


Nova is used via Amazon Bedrock APIs, in particular InvokeModel, InvokeModelWithResponseStream, Converse, ConverseStream, and, for Sonic, via bidirectional streaming.

## Claim
LLM “frontier intelligence” - “industry-leading price-performance”

## Geeignet für
- API Integration
- Audio / Voice
- Automation / Workflows
- Education
- Data Analysis
- Data Extraction / Document Analysis
- Email / Communication
- Customer Service & Chatbots
- Marketing & Advertising
- Programming / Software Development
- Research
- Writing & Editing
- Texts / Content
- Sales / Sales
- Video
- Knowledge Management / Internal Search

## Kernfunktionen
- Image generation
- Function calls
- AI agents
- LLM API
- Multimodal AI
- Language model
- Text generation
- Video generation

## Preismodell
- **free:** AWS shows “Get started for free,” but for Amazon Nova/Bedrock, publicly documented billing is primarily usage-based; specific free quotas depend on AWS offerings, region, and account.
- **other:** **On-Demand / Standard Tier** Usage-based inference by model, modality, and tokens or image/video/special usage.


**Flex / Priority / Reserved Tiers** Bedrock supports different service tiers to manage cost, availability, latency, and throughput.


**Batch Inference **Asynchronous processing of larger workloads; according to AWS, cheaper than On-Demand for selected models.


**Provisioned Throughput** Reserved capacity for higher or predictable throughput; required for certain custom or production scenarios.


**Fine-Tuning / Custom Models** Customization using your own training/validation data; use of individual models typically via provisioned capacity.


**Guardrails / Knowledge Bases / Agents / Prompt Routing **Additional Bedrock features for security, RAG, agent orchestration, model routing, and governance.

## DSGVO und Datenschutz
**Gesamteinschätzung:** Conditional

**On-premises / local hosting: indirect / not available**


The website does not mention a true on-premises/local deployment of Amazon Nova on the customer’s own hardware. The only documentation states that customers can establish private connectivity between a customized Nova instance and on-premises networks via AWS PrivateLink; this is not a local deployment of the model.


**Private Cloud / Data Center: Partially**


Documented features include in-region processing, EU-geographic routing, VPC/PrivateLink connectivity, as well as encryption and IAM/KMS controls. This points to a highly controllable cloud environment, but not to a dedicated, customer-owned private cloud instance of Nova in the strict sense.


**EU SaaS / Managed: Partially**


Amazon Nova is available as a managed service via Amazon Bedrock, and Bedrock documents in-region and EU-geographic data residency options. However, no blanket “EU-only” standard is described for all Nova uses; EU-compliant data residency depends on the specific region and routing selection.


**Hybrid: Partially**


The website documents private connectivity between customized Amazon Nova and on-premises networks via AWS PrivateLink. This enables hybrid architectures in which internal systems are connected, even if the model itself runs as an AWS service.


**T&C / DPA: Covered**


AWS documents a “GDPR-compliant AWS Data Processing Addendum (AWS DPA),” which automatically applies to customers and is integrated into the AWS Service Terms. Additionally, AWS refers to SCCs and supplementary addenda for data transfers.


**No training: covered**


The website explicitly states that AWS does not use inputs or outputs from Amazon Bedrock to train Amazon Bedrock models, including Amazon Nova. Furthermore, Bedrock documents “Zero Data Retention” as a configurable option; however, by default, retention periods may be relevant for abuse detection depending on the model, which is why the specific configuration remains important.


**Open Source / Transparency Path: Indirect / Not Available**


The website does not mention an open-source model, disclosed core components, or an explicit open-source/self-hosting path for Amazon Nova. On the contrary, it is documented that Nova weights are proprietary.


**Data Processing**


Amazon Nova is operated as an AWS/Bedrock-based managed service. According to the documentation, requests can be processed strictly within a single AWS region or remain within an EU geography. According to the Bedrock documentation, model providers do not have access to the model deployment accounts operated by AWS, nor to logs, prompts, or completions. According to the documentation, data is encrypted in transit and at rest; KMS can be used. It is also documented for Amazon Bedrock that, by default, inputs and outputs are not used to train Bedrock models and that zero data retention is configurable, with model- or security-related exceptions for retention documented separately.


**Conclusion**


For a tool directory focused on the EU/EEA, Amazon Nova cannot be generally considered fully GDPR-compliant in the sense of “out of the box in every case,” but there is substantial evidence on the AWS platform for **conditional** GDPR-compliant use: DPA, SCCs, EU/region-based control, encryption, and a clear “no training” policy. It is crucial that customers select the correct Bedrock region or EU geography and do not use global or otherwise transfer-intensive operating modes. According to the documentation found, on-premises and open-source sovereignty are not available for Nova.


**Sources**


- [https://docs.aws.amazon.com/nova/latest/userguide/what-is-nova.html](https://docs.aws.amazon.com/nova/latest/userguide/what-is-nova.html)
- [https://docs.aws.amazon.com/nova/latest/userguide/responsible-use.html](https://docs.aws.amazon.com/nova/latest/userguide/responsible-use.html)
- [https://docs.aws.amazon.com/bedrock/latest/userguide/models-region-compatibility.html](https://docs.aws.amazon.com/bedrock/latest/userguide/models-region-compatibility.html)
- [https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html](https://docs.aws.amazon.com/bedrock/latest/userguide/data-protection.html)
- [https://docs.aws.amazon.com/bedrock/latest/userguide/data-encryption.html](https://docs.aws.amazon.com/bedrock/latest/userguide/data-encryption.html)
- [https://docs.aws.amazon.com/bedrock/latest/userguide/abuse-detection.html](https://docs.aws.amazon.com/bedrock/latest/userguide/abuse-detection.html)
- [https://docs.aws.amazon.com/whitepapers/latest/navigating-gdpr-compliance/aws-data-processing-addendum-dpa.html](https://docs.aws.amazon.com/whitepapers/latest/navigating-gdpr-compliance/aws-data-processing-addendum-dpa.html)
- [https://docs.aws.amazon.com/whitepapers/latest/navigating-gdpr-compliance/in-detail.html](https://docs.aws.amazon.com/whitepapers/latest/navigating-gdpr-compliance/in-detail.html)
- [https://docs.aws.amazon.com/nova/latest/userguide/nova-model-training-job.html](https://docs.aws.amazon.com/nova/latest/userguide/nova-model-training-job.html)

The documentation on the AWS website outlines several components for GDPR-compliant use in the EU/EEA context: AWS references a GDPR-compliant DPA, refers to SCCs for international transfers, describes Bedrock/Nova as capable of being supported in a GDPR-compliant manner, and documents in-region and EU-specific processing options. At the same time, the documentation found does not allow for the inference of a comprehensive, automatic “EU-only” default configuration for all Nova scenarios; compliance depends on the specific region selected, the chosen Bedrock routing, and the customer’s configuration. Therefore, from an EU/EEA perspective, its use can **only** be considered GDPR-compliant **under certain conditions**.


**Positive**


Positive aspects include an AWS Data Processing Addendum, which, according to AWS, is GDPR-compliant and applies automatically; SCCs or additional safeguards for transfers; the option for processing in an EU region; references to EU-based data residency with Bedrock routing; encryption at rest and in transit, customer-managed key management, and the statement that inputs/outputs via Amazon Bedrock are not used to train Amazon Bedrock models, including Amazon Nova.


**Negative**


A negative or limiting aspect is that the documentation for Amazon Nova itself does not guarantee a blanket EU/EEA-only operating mode as the standard for all usage scenarios. In addition to in-region routing, Bedrock offers geo- and global routing; for GDPR-sensitive cases, the customer must therefore actively select the appropriate option. The website does not specify an explicit Nova-specific server location for all functions, a Nova-specific list of subprocessors, an explicit self-hosting/on-premises deployment of Nova, or a clear statement regarding open-source components.


**Server Location**


The website documents for Amazon Bedrock that in-region processing remains strictly within the selected region and that geo-routing can occur within a geographic area such as the EU. For Amazon Nova, the Bedrock regional table lists at least one EU region as available, namely 'eu-north-1 (Stockholm)' for Nova 2 Sonic. A general, central server location for Amazon Nova is not specified on the website.

## Hosting und Daten
- **On-Prem / lokales Hosting:** unknown
- **Private Cloud / Rechenzentrum:** teilweise / indirekt
- **EU SaaS / Managed:** teilweise / indirekt
- **Hybrid:** teilweise / indirekt
- **AVV / DPA:** abgedeckt
- **Kein Training auf Kundendaten:** abgedeckt
- **Open-Source / Transparenz-Pfad:** unknown

## Standort
**Land:** USA

**Taxonomie:** USA

For AWS in general, officially documented, among others, is Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109-5210, U.S.A.

## Vorteile
- Strong AWS integration.
- No training with customer data according to AWS.
- EU regions or EU geo-inference available for several Nova models.
- Good model tiering from inexpensive/fast to powerful.
- Multimodal models for text, images, video, documents, and code.
- Strong enterprise controls via AWS IAM, VPC/PrivateLink-like architecture, CloudTrail, CloudWatch, KMS, and Bedrock Guardrails.

## Nachteile
- No self-hosting of the Nova model weights.
- No open-source/open-weights path.
- Prices depend heavily on the model, region, service tier, and token consumption.
- Some models are only available in certain regions.
- Nova Canvas and Nova Reel are Nova models, but not LLMs.
- For GDPR projects, region, cross-region inference, logging, guardrails, retention, and the AWS contract must be configured properly.

## Quellen
- Offizielle Website: https://docs.aws.amazon.com/nova/latest/userguide/what-is-nova.html

## Letzter Datenstand
2026-04-25

## Originalseite
https://kifox.ai/en/ki-tools/amazon-nova-api-en/