100%
GRIMOIRE
GrimoireDindon CorpusSynthesis VolumesThe Foundation of Iron
FRENAR
RATIO
STRUCTURAL STUDY · OPÉRATION DINDON · JUNE 2026
◆◆◆
TERMS OF SERVICE
UNDER THE
MICROSCOPE
AWS & GCP — Corpus Reading
What the Terms of Service Say That the Brochures Do Not
◆ METHODOLOGY

This study analyses the Terms of Service of AWS (June 2026 version) and Google Cloud Platform in light of the Opération Dindon corpus. Each identified clause is paraphrased — never quoted verbatim — and placed alongside the corpus study that documents its effect. The objective is not legal. It is to show that what the corpus named — cognitive capture, infrational loop, lock-in, loss of sovereignty — is literally inscribed in the contractual documents that European organisations sign every day.

◆◆◆
DOCUMENTS
AWS + GCP
CLAUSES ANALYSED
8
WATERMARK
RATIO
Amine RAITI — Infrastructure Architect & SRE
Former engineering school professor · Teaching since 2006
Public document · CC BY-NC-SA 4.0 · Opération Dindon · June 2026
RATIO
CLAUSE 1 · JURISDICTION — THE DIGITAL GROUND IN THE CONTRACT
EUROPEAN DATA UNDER US LAW — THE TERMS OF SERVICE SAY SO EXPLICITLY
◆ WHAT GCP SAYS — CALIFORNIA JURISDICTION (Section 14.12)

The Google Cloud Platform Terms of Service stipulate, for all entities that are not US government entities, that the law of the State of California governs the contract — excluding California's conflict of laws rules — and that the competent courts are those of Santa Clara County, California. The European customer who signs the GCP Terms therefore accepts that any dispute be resolved under California law, by Californian courts.

What this means concretely: the data of a French hospital, a Belgian bank or a German public authority hosted on GCP are contractually subject to US law. The GDPR applies to collection and processing — but the contractual reference framework is the law of the State of California.

◆ WHAT AWS SAYS — ACCESS UNDER GOVERNMENT ORDER

The AWS Terms of Service specify that the company may act in accordance with any applicable judicial, regulatory or governmental order or request. In the event of content removal without prior notice, AWS will notify the customer promptly — unless prohibited by law. This formulation — "unless prohibited by law" — is precisely the window of the CLOUD Act and National Security Letters: a non-disclosure order (gag order) is legally possible, and the Terms of Service anticipate it.

◆ CORPUS LINK — "THE DIGITAL GROUND" · "NO SOVEREIGNTY WITHOUT MATTER"

The Opération Dindon corpus documented in "The Digital Ground" that AWS and GCP European datacentres do not create European sovereignty — because the applicable jurisdiction for data remains American. This study demonstrates that this is not a corpus interpretation — it is textually inscribed in the Terms of Service. The California jurisdiction clause of GCP and the government access clause of AWS are the contractual proof of the Digital Ground thesis.

The 8 September 2026 ultimatum demands resiliable commits, reasonable egress fees, real portability, and the CLOUD Act limited to its territory. The California jurisdiction clause demonstrates that the fourth demand is the most fundamental: without a change of jurisdiction, the other three are insufficient.

RATIO
CLAUSE 2 · UNILATERAL MODIFICATION — THE INFRATIONAL IN THE CONTRACT
THEY CAN CHANGE PRICES AND CONDITIONS — AT ANY TIME
◆ WHAT GCP SAYS — FEE REVISIONS (Section 2.6)

Google reserves the right to change fees at any time, unless otherwise expressly agreed in an addendum or Order Form. For GWS, Looker and Cloud Identity services, Google commits to 30 days advance notice. But for GCP — the core cloud services — no notice period is mentioned. The formulation "at any time" is explicit.

This unilateral modification of pricing is also conditional: if the customer disagrees with a GCP pricing change, they may terminate for convenience — but under the termination conditions described elsewhere, which include deadlines and obligations.

◆ WHAT AWS SAYS — RESERVED INSTANCE MODIFICATIONS

AWS states it may change Savings Plans, EC2 Reserved Instances and Dedicated Host Reservation pricing at any time — but price changes do not apply to already-purchased reservations. However, if Microsoft increases Windows licence fees or Red Hat increases RHEL fees, AWS may pass these increases on with 30 days notice, including to existing Reserved Instances.

The cascade mechanism: AWS is not the only variable. Its own suppliers' (Microsoft, Red Hat, Oracle) price increases can be passed to the end customer without that customer having any recourse up the chain.

◆ WHAT AWS SAYS — NON-CANCELLABLE COMMITS

For Savings Plans, EC2 Reserved Instances, Capacity Blocks, DB Savings Plans and SageMaker AI Savings Plans, AWS Terms specify that commitments are non-cancellable and that the customer will be charged for the full duration of the selected term, even if the agreement is terminated. Amounts paid are non-refundable, unless AWS terminates the agreement other than for cause.

◆ CORPUS LINK — FIRST ULTIMATUM DEMAND: "RESILIABLE COMMITS"

The first of the four 8 September 2026 demands is: resiliable commits. AWS Terms document precisely the opposite: commitments are "noncancellable". The corpus thesis is verified by the contractual text. This is not an opinion — it is a clause.

RATIO
CLAUSES 3 & 4 · SUSPENSION & TERMINATION — THE ASYMMETRIC POWER
THEY CAN CUT — YOU CANNOT LEAVE
◆ UNILATERAL SUSPENSION — AWS AND GCP

AWS: AWS may suspend or terminate access to any Beta service at any time, without notice. For generally available services, suspension is possible on governmental or judicial order, or if AWS judges that the security of its services is threatened. Depending on the service, termination may occur with varying notice periods.

GCP: Google may suspend all or part of access to the services if it reasonably believes suspension is needed to protect the services, other customers or third parties. Google may also suspend immediately to comply with any applicable Legal Process. The suspension may precede notification — if the law permits.

◆ DATA AFTER TERMINATION — THE 30-DAY WINDOW

AWS (Supply Chain N-Tier): when the service ends, the customer has 30 days following termination to retrieve their content. After this deadline, the content will be removed. This formulation — present in several AWS Terms sections — is the migration window: 30 days to export years of structured data, in a format that may not be interoperable with the target system.

GCP: upon termination, all rights to access the services (including access to Customer Data, if applicable) cease. The precise conditions for post-termination data retention and export refer to the Service Specific Terms — a separate document not integrated into the general Terms analysed here.

◆ GCP — TERMINATION FOR CONVENIENCE BY GOOGLE (Section 8.5)

For GCP and TSS services only, Google may terminate the agreement or any applicable Order Form for its own convenience at any time with 30 days prior written notice. The customer may also terminate for convenience at any time on written notice — but must immediately cease using the services upon termination. The asymmetry is structural: Google can terminate for convenience with 30 days notice. The customer can too — but immediately loses access to data and services.

◆ CORPUS LINK — "THE GENTLE EXIT" · "THE SOVEREIGN INTERFACE"

The Gentle Exit proposed in the corpus describes progressive migration, service by service. The 30-day Terms window says the opposite: exit is necessarily abrupt if imposed by the provider. The Sovereign Interface documented in the corpus is precisely the architectural response to this constraint: decouple application code so that migration is not an emergency.

RATIO
CLAUSES 5 & 6 · LIABILITY LIMITATION & INDEMNIFICATION — THE LEGAL ASYMMETRY
YOU ASSUME — THEY LIMIT — YOU DEFEND — THEY ARE DEFENDED
◆ LIABILITY LIMITATION — AWS AND GCP

AWS: the aggregate liability of AWS and its affiliates for Beta services is limited to the amount actually paid by the customer during the 12 months preceding the claim. For generally available services, the same logic applies with similar caps per Customer Agreements. Indirect, consequential, special or punitive damages are excluded.

GCP: neither party will have liability for indirect, consequential, special, incidental or punitive damages, or for lost revenues, profits, savings or goodwill. The limitation applies to the extent permitted by applicable law. Aggregate amounts are capped per the Service Specific Terms.

The asymmetry: if an AWS or GCP failure causes €10 million in lost business for a customer organisation, the provider's contractual liability will be limited to fees paid over 12 months — perhaps €50,000. The gap between actual loss and contractual compensation is structural.

◆ ASYMMETRIC INDEMNIFICATION — THE CUSTOMER DEFENDS THE PROVIDER

GCP: the customer agrees to defend Google and its affiliates against any third-party legal proceeding arising from the customer's non-compliant use of the Terms, or from a claim that customer data infringes third-party intellectual property rights.

AWS: Marketplace sellers indemnify AWS and its affiliates against any transaction-related tax claims. More generally, the customer is responsible for all use under their account, including by their end users.

The structure: Google defends the customer against claims concerning Google's services (Google's intellectual property). The customer defends Google against claims concerning customer usage. Usage liability migrates to the customer. Platform liability stays with Google but is capped.

◆ CORPUS LINK — "THE STATE AND THE INVISIBLE BODY" · "NO SOVEREIGNTY"

The corpus documents the absence of infrastructure body protection by the State. This clause shows that protection does not exist in the contract either: provider liability is capped, customer liability on usage is unlimited. The sovereign organisation is the one that does not depend on an asymmetric contract for its business continuity.

RATIO
CLAUSES 7 & 8 · CERTIFICATIONS & PORTABILITY — CAPTURE THROUGH KNOWLEDGE
CERTIFICATIONS AS A DEPENDENCY TOOL · PORTABILITY ABSENT
◆ THE AWS CERTIFICATION PROGRAMME — THE INFRATIONAL LOOP IN THE CONTRACT

The AWS Terms include a dedicated article on the "AWS Certification Program" — a service in its own right subject to a separate agreement (Certification Program Agreement, CPA). AWS certification certifies that a person has passed a proficiency test on a specific AWS service or domain. It is not transferable between providers and does not guarantee the quality of services delivered by the certified provider.

What this says about the job market: an AWS certification is an employable asset on the AWS market — and only on that market. An AWS Certified Solutions Architect has an asset worth something on AWS projects. There is no equivalent certified on GCP, Azure, or on bare-metal. A CPF budget funding an AWS certification funds dependency — not neutral competence.

What the Terms confirm: the certification programme is a "Service" under the Terms of Service. AWS defines its conditions, may modify programme terms, and the CPA supersedes the general agreement in case of conflict. The certification belongs to the AWS ecosystem — not to the engineer.

◆ DATA PORTABILITY — THE REVEALING ABSENCE

Neither the AWS Terms analysed, nor the GCP Terms analysed, contain a clause guaranteeing data portability in a standard, interoperable format, at no additional cost. Searching for "portability" in both documents returns only:

— AWS: telephone number portability in Amazon Chime and Amazon Connect (telephony portability, not cloud data portability).
— GCP: HIPAA (Health Insurance Portability and Accountability Act) — a US healthcare law, not a cloud data portability guarantee.

The absence is the data point: in 302,000 characters of AWS Terms and 113,000 characters of GCP Terms, the term "data portability" in the sense of a guaranteed export in a neutral format at no additional cost is absent. These are the second and third ultimatum demands — "real portability" and "reasonable egress fees" — that the Terms do not address.

◆ CORPUS LINK — "THE CPF MISUSED" · "THE INFRATIONAL LOOP" · ULTIMATUM

The CPF Misused documents that training budgets flow to proprietary cloud certifications. The AWS Terms confirm that these certifications are AWS services, governed by AWS law, terminable by AWS. The loop is complete: public money funds competences that belong to the ecosystem of an extraterritorial actor.

RATIO
SYNTHESIS — THE TERMS OF SERVICE AS CONTRACTUAL PROOF OF THE CORPUS
CORRESPONDENCE TABLE — TERMS CLAUSE × CORPUS STUDY × ULTIMATUM DEMAND
TERMS CLAUSE
WHAT IT SAYS
CORPUS STUDY
ULTIMATUM DEMAND
GCP §14.12 — California law
Any dispute resolved under California law, Santa Clara courts
The Digital Ground · No Sovereignty Without Matter
4. CLOUD Act limited to its territory
AWS — Government access
Disclosure possible under government order, no notice if law prohibits
The Digital Ground · Anatomy of the Loss
4. CLOUD Act limited to its territory
GCP §2.6 — Fees "at any time"
Google may change GCP fees at any time with no guaranteed notice
The Infrational Loop · FinOps of the Last Gram
2. Reasonable egress fees
AWS — "Noncancellable" commits
Reserved Instances, Savings Plans: billed even if agreement is terminated
Anatomy of the Loss · The Gentle Exit
1. Resiliable commits
AWS/GCP — Unilateral suspension
Suspension possible at any time, immediately for "Legal Process"
The Digital Ground · The State and the Invisible Body
1 + 4. Resiliable commits + CLOUD Act
AWS/GCP — Data: 30 days post-termination
30 days to retrieve data — then deletion. No neutral format guarantee.
The Gentle Exit · The Sovereign Interface
3. Real portability
AWS/GCP — Liability limitation
Liability capped at last 12 months' fees. Indirect damages excluded.
The Economy of Silence · The State and the Invisible Body
All 4 demands
AWS — Certifications as proprietary service
AWS Certification Programme is an AWS service under a separate AWS agreement
The CPF Misused · The Infrational Loop
3. Real portability (of competences)
AWS/GCP — Portability absent
No clause guaranteeing data export in a neutral format at no additional cost
No Sovereignty · The Sovereign Interface
2 + 3. Egress fees + Portability
RATIO
CONCLUSION — WHAT THE TERMS PROVE THAT THE CORPUS NAMED
THIS IS NOT AN OPINION — IT IS IN THE CONTRACT YOU SIGNED
◆ WHAT THIS ANALYSIS DEMONSTRATES

The Opération Dindon corpus named phenomena — cognitive capture, infrational loop, loss of sovereignty, lock-in, extraterritorial dependency. These phenomena could have been contested as interpretations, opinions, or rhetorical exaggerations. This analysis of the Terms of Service demonstrates that they are textually inscribed in the contractual documents that European organisations sign every day:

— GCP's California jurisdiction is in Section 14.12.
— The unilateral fee modification "at any time" is in GCP Section 2.6.
— "Noncancellable" commits are in the AWS Reserved Instances, Savings Plans and Capacity Blocks sections.
— Suspension on "Legal Process" without mandatory prior notice is in both Terms.
— Data portability in a neutral format is absent from both documents.
— Liability limitation to last 12 months' fees is in both Terms.
— The AWS Certification Programme is a proprietary service governed by a separate agreement.

◆ THE FOUR 8 SEPTEMBER 2026 DEMANDS — JUSTIFIED CLAUSE BY CLAUSE

1. Resiliable commits: justified by the "noncancellable" clauses in AWS Savings Plans, Reserved Instances, Capacity Blocks, DB Savings Plans.
2. Reasonable egress fees: justified by the absence of any clause governing outbound transfer fees, and by the possible fee revision "at any time" in GCP.
3. Real portability: justified by the absence of any clause guaranteeing data export in a neutral format at no additional cost, and by the 30-day post-termination window.
4. CLOUD Act limited to its territory: justified by GCP's California jurisdiction clause (Section 14.12) and AWS's government access clause that anticipates legal non-disclosure orders.

◆◆◆

The Opération Dindon corpus did not invent these problems.
It named them before you read the Terms of Service.
The Terms of Service confirm what the corpus said.
The hyperscalers' silence does too.

◆◆◆
NEMO SUPRA LEGEM EST