Skip to content

Model catalogue · Amazon Web Services

Amazon Nova

Amazon Web Services' own language model line, graded from a large through a medium to a lean tier: condensing files and annexes, drafting correspondence, pulling details from documents - the tiers differ in speed and cost, not in handling. Via Amazon Bedrock the defaults are unusually favourable: neither operator staff nor a model vendor gets access to inputs and outputs, and nothing is stored in the delivered state. The chain is nevertheless not closed, because no signable standard document for the confidentiality undertaking under section 203 of the German Criminal Code is evidenced for this route; on top of that, binding to the EU is a per-call decision in code and not an account switch.

Usable, but one piece is still open

You can work with it - but part of the safeguard is open: either the provider does not commit to confidentiality itself, or it depends on an agreement you still have to conclude. Which of the two applies to which route is set out in the full matrix.

What it is good for

  • Zero retention and the absence of operator access are the default of this route, not an exception applied for
  • Graded tiers from Premier to Lite - the same contractual position for all, different cost and latency classes
  • Processing in European regions through region-bound calls or the eu inference profile

Where it stops

  • The eu inference profile routes within Europe - depending on the profile the target lists also include regions outside the EU member states (London, Zurich). Anyone with 'EU member state' as a requirement checks the profile's target list individually or binds the call to a region
  • A worldwide profile exists for the same models; without an organisational policy the EU location is a per-call decision in code
  • No legal fine-tuning; references and deadlines remain subject to the practitioner's review

Routes examined

The same model, procured differently, is a different legal position. What is examined per route is the contract chain, not the model.

Route Section 203 status Version on this route
AWS Bedrock (EU region Frankfurt) conditional -

The conditions behind a conditional status - which piece is open on which route and who closes it - are set out in the full matrix in the German catalogue, and we go through them in the conversation. The German page for Amazon Nova carries the sources with their retrieval dates.

Is Amazon Nova the right fit?

We go through your tasks and the route that carries them - and say plainly where it does not.

Arrange a conversation