Addressing sovereignty concerns: Privacy, compliance & vendor lock-in
summary
AWS claims a technical and contractual sovereignty stack: the Nitro system and zero operator access isolate hypervisor, 38 regions each with ≥3 AZs and a 6 million km fiber backbone, and 96% of network events auto‑remediate. Data protection uses AWS KMS with customer‑managed and BYOK plus double encryption via external key stores and FIPS‑validated HSMs. Transparency shows zero Cloud Act disclosures outside the US since 2020, a Swiss addendum, and cases like Swiss Post able to switch platforms in 1–2 weeks and cut infrastructure cost ~90%.
AI-written summary · about
chapters (9)
- 0:00Introduction to sovereignty concerns
- 3:21Operational resilience in AWS
- 8:06Privacy and data protection
- 17:30Addressing the Cloud Act
- 21:47Contractual protections for customers
- 24:41Data residency and compliance
- 32:13Avoiding vendor lock-in
- 39:52Sovereignty pyramid summary
- 44:38Closing and next steps
related talks
17mControl without compromise: AWS European Sovereign Cloud
17mChoosing the right cloud infrastructure for digital sovereignty
49mSwisscom's pioneering journey to run regulated workloads on AWS(SEC205)
15mNavigate sovereignty complexity with the AWS European Sovereign Cloud
32mBuild without limits with AWS Cloud infrastructure
53mKeep Calm & Run on AWS: Compliance While Keeping Your Stack
03mCustomer Spotlight
46mEnhance security with the AWS Nitro System