Sovereign Cloud - From Mirage to Epiphany
summary
Argues that sovereign cloud shifts from niche to necessity, driven by geopolitics, GDPR-style privacy and supply‑chain rules, and messy hybrid stacks; cites surveys: 42% of orgs have repatriated apps, 32% are moving apps and only 16% never touched repatriation, with ~20% accidentally hybrid. Recommends concrete fixes: governance + manageability + controls, a sovereignty-as-code approach, sovereignty dashboards, choice between sovereign hyperscaler, local providers or on‑prem, and warns that failures (e.g., CrowdStrike) come from testing and contract gaps.
AI-written summary · about
chapters (9)
- 0:00Sovereign Cloud keynote
- 1:02Technological sovereignty challenges
- 5:01Drivers of sovereignty today
- 10:19Cloud repatriation strategies
- 12:48Sovereignty definitions
- 16:40Sovereign Cloud options
- 22:42Delivery challenges and governance
- 27:20Sovereignty as business asset
- 31:33Q&A
related talks
44mState of Cloud Sovereignty: From Public Clouds to…
38mState of Cloud Sovereignty: From Public Clouds to Confidential Clouds
52mHow Sovereign Solution Providers are Securing Europe’s Digital Borders?
26mDigital sovereignty: between myth and reality How to arbitrate
29mSovereign Cloud Initiative & Wrap Up
48mCloud Advisory: Cloudy, with a chance of people
08h 05mThe European Sovereign Cloud Day
19mHow Do We Get Control of Our Data? The Struggle for Digital Sovereignty