Latest / Best of LinkedIn: Digital Transformation & Tech / Best of LinkedIn: Cloud Insights & Sovereignty CW 41/ 42

Transcript

Best of LinkedIn: Cloud Insights & Sovereignty CW 41/ 42 · Best of LinkedIn: Digital Transformation & Tech

• 0:00
  Speaker 0: Provided by Thomas Allgaier and Franis, based on the most relevant LinkedIn posts about cloud insights in sovereignty.
• 0:05
  Speaker 0: In calendar weeks forty one and forty two.
• 0:08
  Speaker 0: Franus has built a sovereign cloud market radar for ICT providers with weekly hot news monthly reports quarterly leadership presentations and AI podcast for field teams.
• 0:19
  Speaker 0: you can find more info in the description.
• 0:21
  Speaker 0: so today We're doing an executive briefing on the top digital products and services trends across LinkedIn.
• 0:27
  Speaker 0: And it's really curated specifically for you that tech professionals managing digital transformation right now,
• 0:33
  Speaker 1: Right?
• 0:33
  Speaker 1: Because we are cutting right through the noise surrounding cloud architecture AI economics in governance to find the actual signal here were starting with a real bedrock of modern infrastructure which is well where your data physically lives and the engineering reality of who truly controls it.
• 0:50
  Speaker 0: Okay, let's unpack this because the word sovereignty gets thrown around in boardrooms so casually now?
• 0:56
  Speaker 0: It's kind
• 0:59
  Speaker 1: become just a legal checkbox.
• 1:01
  Speaker 1: But we need to move it into the realm of hard-coded engineering reality.
• 1:05
  Speaker 1: Bertrand Legra actually surfaced really brilliant framework for this.
• 1:09
  Speaker 1: Yeah,
• 1:09
  Speaker 0: The Six Questions
• 1:10
  Speaker 1: Exactly.
• 1:11
  Speaker 1: He argues that calling a cloud sovereign actually hides six distinct highly technical questions.
• 1:17
  Speaker 1: You have know where data sits whose legal jurisdiction reaches who physically holds encryption keys
• 1:23
  Speaker 0: And whether infrastructure keeps running if vendor relationship catastrophically fails
• 1:28
  Speaker 1: Right and whether you can actually build on it.
• 1:31
  Speaker 1: And finally, if its politically acceptable to rely on that specific foreign provider.
• 1:37
  Speaker 1: what's fascinating here is the most crucial distinction LaGrosse makes is fundamentally separating sovereignty from resilience
• 1:43
  Speaker 0: Which people mix up all of time?
• 1:45
  Speaker 1: Constantly.
• 1:47
  Speaker 1: Resilience is availability under failure like a fiber cut or server fire You solve with redundancy.
• 1:53
  Speaker 1: Sovereignty Is Availability Under Decision In executive order or a sudden sanction.
• 1:59
  Speaker 0: Right?
• 2:00
  Speaker 0: And that tension is playing out live at the hardware level right now, Fadi D'Souz flagged this massive development where AWS's running alive tests to actually cut off their European sovereign cloud from global AWS backbone.
• 2:13
  Speaker 1: They're physically severing it
• 2:15
  Speaker 0: Literally intentionally severing digital connection To prove datacenters can operate independently inside EU operated solely by EU residents without calling home to US servers.
• 2:27
  Speaker 1: I mean, it is a serious engineering flex to sever the backbone of a hyperscaler and prove that lights stay on.
• 2:33
  Speaker 1: Wait
• 2:33
  Speaker 0: but let me push back on this exact point though... If The U.S.
• 2:36
  Speaker 0: Cloud Act still applies because the parent company's American aren't we just buying a highly resilient data center and slapping a sovereign sticker?
• 2:44
  Speaker 1: That is the big debate!
• 2:46
  Speaker 0: Right Because the law historically doesn't care where server rack physically sits It cares who owns the subsidiary.
• 2:52
  Speaker 0: So if a subpoena lands in Seattle ...the data in Frankfurt is still compromised
• 2:56
  Speaker 1: And that exact legal friction is driving a completely different architectural approach.
• 3:01
  Speaker 1: Harold Yos highlighted the model being built with the Thales-operated Google Sovereign Cloud.
• 3:05
  Speaker 0: Oh, The Separation of Duties?
• 3:06
  Speaker 1: Exactly!
• 3:07
  Speaker 1: Thales which an independent German owned entity holds operative control and the sole encryption keys.
• 3:13
  Speaker 1: Google provides underlying hypervisors in storage but they are COMPLETELY blind – They mathematically cannot decrypt workload.
• 3:20
  Speaker 0: So their building operator US government legally can't compel?
• 3:24
  Speaker 1: Precisely because the parent company doesn't have the keys.
• 3:28
  Speaker 0: But, The problem extends way past the provider's corporate structure right?
• 3:32
  Speaker 0: It is buried in your own application code.
• 3:34
  Speaker 0: Harry Malonis warned that most of these shiny multi-cloud policies that Corporate Boards are rubber stamping Are going to fail.
• 3:40
  Speaker 0: a Dora exit test.
• 3:41
  Speaker 1: And we should clarify, a Dora exit test driven by the EU's Digital Operational Resilience Act is not just a paperwork drill.
• 3:49
  Speaker 1: No!
• 3:49
  Speaker 1: Not at all.
• 3:50
  Speaker 1: You have to prove you can physically move your critical workloads elsewhere if a vendor collapses.
• 3:54
  Speaker 0: Exactly and Milona's points out organizations are confusing provider sovereignty with architectural excitability.
• 4:01
  Speaker 0: Provider Sovereignty Just means that hyperscaler cant read data but Architectural Exitability Means you Can actually pack up & leave
• 4:09
  Speaker 1: Right, if you're hard-coded to AWS IAM.
• 4:12
  Speaker 1: You can't exit
• 4:13
  Speaker 0: Yep If your microservice authorization is irreversibly tied there or your AI reasoning loops are bound to Amazon bedrock?
• 4:21
  Speaker 0: You physically cannot exit that cloud...you move the data The application breaks.
• 4:25
  Speaker 1: This really ties into the core argument from Peter DeLorenzo.
• 4:29
  Speaker 1: He says true sovereign team means having the engineering capability To switch providers..if a code traps you....You want Sovereign!
• 4:35
  Speaker 1: You just negotiated A longer lease.
• 4:37
  Speaker 0: Just uh New landlord.
• 4:39
  Speaker 1: Exactly, and Bert DeSmet notes the regulatory heat is turning up.
• 4:43
  Speaker 1: The EU-CADA proposal level two sets audited sovereignty requirements.
• 4:47
  Speaker 1: We're talking mandatory local support models complete software bills of materials.
• 4:52
  Speaker 0: So major US hyperscaler sovereign editions might actually fail these audits?
• 4:57
  Speaker 1: They might because self declaration isn't enough anymore.
• 5:00
  Speaker 1: Auditors want to see the architecture.
• 5:02
  Speaker 0: But despite all these hurdles that deployment momentum is very real.
• 5:07
  Speaker 0: Stephen Wagner from SAP stated, digital sovereign trees basically an engineering challenge requiring strong local ecosystems.
• 5:15
  Speaker 1: And we're seeing them stand up?
• 5:17
  Speaker 0: We are.
• 5:18
  Speaker 0: Ash Thanky noted the Brandenburg Medical University is using the AWS European Sovereign Cloud to connect a regional health network and Harriet Reese shared that Starling is the first UK bank to train AI on a UK sovereign cloud via SIVO
• 5:33
  Speaker 1: which ensures domestic financial data never leaves domestic infrastructure during training.
• 5:38
  Speaker 1: And if true sovereignty requires you to be able to cleanly exit a cloud environment, You really have to prioritize architectural freedom above all else.
• 5:47
  Speaker 1: This is triggering massive resurgence of private cloud To avoid commercial lock-in.
• 5:52
  Speaker 1: Public and private Cloud Parity Is making workload placement an architectural choice again Not a constraint.
• 5:58
  Speaker 0: But how do you justify that capital expense to a board that spent a decade demanding public cloud?
• 6:04
  Speaker 0: Brian White highlighted, A perfect catalyst.
• 6:07
  Speaker 0: Broadcom's decision to deauthorize insight enterprises as a VMware reseller
• 6:12
  Speaker 1: Yeah That was huge.
• 6:14
  Speaker 0: So what does this all mean?
• 6:16
  Speaker 0: It's like renting a fully furnished apartment.
• 6:19
  Speaker 0: You've lived there for years.
• 6:21
  Speaker 0: Then without warning the landlord decides To triple the rent specifically on The couch you sit On every day.
• 6:26
  Speaker 0: I love
• 6:26
  Speaker 1: that analogy.
• 6:27
  Speaker 0: Right Your application hasn't changed.
• 6:30
  Speaker 0: Not one line of code, but your financial reality is ruined by a vendor decision.
• 6:35
  Speaker 0: so you have to preserve your freedom to move your own furniture.
• 6:38
  Speaker 1: The market reaction that economic shock has been staggering!
• 6:43
  Speaker 1: Andres Cleaver shared survey data showing nine out ten VMware customers are looking for an exit.
• 6:47
  Speaker 1: Wow...
• 6:47
  Speaker 0: ninety percent
• 6:49
  Speaker 1: Yes, and sixty percent want a multi-hypervisor strategy.
• 6:52
  Speaker 1: They refuse to swap VMware lock in for a different single vendor login.
• 6:57
  Speaker 1: but obviously running multiple hypervisors introduces massive operational complexity.
• 7:02
  Speaker 0: Oh absolutely
• 7:03
  Speaker 1: Which is why providers like HPE are pushing hybrid by design cloud ops platforms Like Morpheus To abstract that complexity And manage it all from a single control plane.
• 7:13
  Speaker 0: The hardware vendors are racing to catch this Exodus too.
• 7:16
  Speaker 0: Michael Redmond noted Nutanix is actively building landing zones where licensing practically maps onto VMware tiers based on the workload.
• 7:23
  Speaker 1: They're trying to make the escape hatch as frictionless as possible.
• 7:27
  Speaker 1: if we connect this to The Bigger Picture, David Linthicum delivered a pretty stark warning.
• 7:32
  Speaker 1: he argues public cloud has silently become exponentially more expensive and it isn't inherently more secure.
• 7:39
  Speaker 0: so his message is stop taking your architecture strategy from the vendor holding the invoice.
• 7:44
  Speaker 1: exactly It flips the cloud first.
• 7:46
  Speaker 1: always assumption to, Cloud only where it makes mathematical sense.
• 7:50
  Speaker 0: And we are seeing industry specific use cases for this.
• 7:53
  Speaker 0: Todd Mason pointed out that a twenty four seven live television broadcast production is way better suited for purpose built private multi-tenant cloud than public one.
• 8:02
  Speaker 0: The latency tolerance just demand dedicated hardware
• 8:06
  Speaker 1: An edge computing another mechanism.
• 8:08
  Speaker 1: Eugene Park highlighted Dell Private Cloud Edge virtualization.
• 8:13
  Speaker 1: Instead of round-tripping real time inventory computer vision data from a store in Chicago to Virginia and back...
• 8:19
  Speaker 0: They just put the compute in the store.
• 8:20
  Speaker 1: Right, it drastically lowers AI inferencing latency And cuts down on truck rolls for IT support.
• 8:26
  Speaker 0: But let's look at the human toll here.
• 8:28
  Speaker 0: Your infrastructure is now spanning audited sovereign zones Edge locations & stores In multi hypervisor private cloud.
• 8:36
  Speaker 0: Human teams are completely overwhelmed.
• 8:39
  Speaker 1: The dashboards are blinking red too fast
• 8:41
  Speaker 0: Way Too Fast.
• 8:43
  Speaker 0: We're just driving this convergence of DevOps, ML Ops and AI into agentic cloud ops.
• 8:48
  Speaker 0: AI is stepping in to operate the Cloud.
• 8:51
  Speaker 1: It's a huge paradigm shift.
• 8:54
  Speaker 1: Carthike NJ and Jill Ferris highlighted The AWS well-architected Agent entering public preview.
• 9:00
  Speaker 1: In the old model an engineer finds An issue reads docs writes terraform code And deploys it.
• 9:06
  Speaker 1: right now the AI agent identifies the anomaly explains the trade-offs and generates the exact prescriptive fixes.
• 9:15
  Speaker 1: The engineer just approves
• 9:16
  Speaker 1: it.".
• 9:16
  Speaker 0: It's wild, like AI isn't suggesting a blueprint name where its pouring concrete.
• 9:22
  Speaker 0: Thomas Fontres pointed out Nokia.
• 9:23
  Speaker 0: AI agents are cutting cloud migration cost assessments from days down to literally minutes.
• 9:29
  Speaker 1: They map dependencies instantly.
• 9:32
  Speaker 0: Here is really interesting though If the AI recommends The Fix, writes the code and evaluates the cost.
• 9:38
  Speaker 0: At what point does human cloud architect just become a rubber stamp?
• 9:42
  Speaker 0: Are they blindly clicking approve?
• 9:44
  Speaker 1: Mark Vigueroso hosted this exact psychological trap.
• 9:49
  Speaker 1: We are risking repeating old Cloud lift-and-shift mistakes with AI agents.
• 9:54
  Speaker 1: If you bolt an agent onto broken deployment process... You get automated chaos at light speed!
• 10:00
  Speaker 0: What's The Fix?
• 10:01
  Speaker 1: Governance first The traditional change advisory board, the cab is dead in an automated world.
• 10:08
  Speaker 1: You have to repulse it with hard-coded automated
• 10:10
  Speaker 1: guardrails."
• 10:11
  Speaker 0: And Yulia Petrishanthian echoed that.
• 10:14
  Speaker 0: she said autonomous operations require a persistent infrastructure context layer.
• 10:20
  Speaker 0: you can't just give an AI API access to Terraform and let it loose.
• 10:24
  Speaker 1: No!
• 10:24
  Speaker 1: It'll optimize one service and break three others.
• 10:27
  Speaker 0: Exactly...it needs semantic understanding.
• 10:30
  Speaker 1: This is forcing disciplines.
• 10:32
  Speaker 1: Ravi Sankara noted DevOps, ML Ops and AI are converging into one governed operating model.
• 10:38
  Speaker 0: And Olivia Caruso pointed out that IBM Bob is now available.
• 10:41
  Speaker 0: on-premises and air gapped which proves trust in governance are officially the AI product not just model size.
• 10:49
  Speaker 0: if a bank can't put its code in public AI The vendor has to bring the AI to the Bank
• 10:54
  Speaker 1: Exactly!
• 10:55
  Speaker 1: Operating those models leads to ultimate reality check which is economics.
• 10:59
  Speaker 1: You can't let AI agents manage your cloud without governing the explosive compute costs.
• 11:05
  Speaker 0: Speaking of managing things real quick, if you are finding these insights valuable should definitely make sure to subscribe to The Feed so that you don't miss future deep dives into digital transformation trends.
• 11:15
  Speaker 0: Alright lets talk FinOps and AI cost.
• 11:19
  Speaker 1: This conversation has matured SO fast.
• 11:22
  Speaker 0: Joe Daly noted FinOps practitioners have stopped debating whether to cap token usage.
• 11:27
  Speaker 0: Now It's about how to build flexible CAFs.
• 11:31
  Speaker 1: Like setting limits based on job roles?
• 11:33
  Speaker 0: Right!
• 11:34
  Speaker 1: A junior PM doesn't need the same token budget as a senior developer, and hitting a CAP doesn't shut you off.
• 11:39
  Speaker 1: it just starts a conversation.
• 11:41
  Speaker 0: Tatiana Boyarshan & Satya Depal Singh shared some great lessons from FinOpsx Amsterdam on this.
• 11:47
  Speaker 0: because measuring AI economics purely by tokens is so flawed?
• 11:51
  Speaker 1: Oh completely...
• 11:52
  Speaker 0: Its like measuring cost of meeting with the number words spoken…it gives you a number but it ignores whether any actual work got done.
• 11:59
  Speaker 1: That is the perfect way to look at it.
• 12:01
  Speaker 1: Singh argues we have to shift to measuring the cost per successful business outcome.
• 12:05
  Speaker 1: if a cheap model requires thirty minutes of human debugging, It's actually more expensive than premium models that get it right instantly.
• 12:12
  Speaker 0: This raises an important question though How do you forecast these outcomes?
• 12:17
  Speaker 0: Diana L argues cloud forecasts based purely on historical spend math are just flawed
• 12:23
  Speaker 1: now.
• 12:23
  Speaker 1: Historical Math Is Stale Math.
• 12:25
  Speaker 0: Exactly.
• 12:27
  Speaker 0: They have to include direct engineering input on upcoming architecture changes.
• 12:31
  Speaker 1: And the visibility tooling is finally evolving for this.
• 12:34
  Speaker 1: Hassan Kajahusani noted infracost as shifting Kubernetes.
• 12:37
  Speaker 1: pod cost estimates left, engineers see the financial estimate directly in their pull request before deployment.
• 12:44
  Speaker 1: That's
• 12:45
  Speaker 0: huge and Ben Schachter noted advantages adding NVIDIA MIG support multi-instance GPU.
• 12:51
  Speaker 0: So instead of renting a whole massive chip and wasting power you slice it up.
• 12:56
  Speaker 0: This means companies can finally allocate costs for partial GPU usage.
• 13:00
  Speaker 1: It's all about precision,
• 13:02
  Speaker 0: but Nicholas Fondrini reframed this beautifully.
• 13:04
  Speaker 0: He says sometimes spending extra upfront on architecture is a Phenops risk premium
• 13:09
  Speaker 1: like buying insurance against lock-in.
• 13:12
  Speaker 0: Yes Spending a bit more to reduce commercial lock in cyber risk and concentration risk
• 13:16
  Speaker 1: which really summarizes the core thread of this entire deep dive
• 13:20
  Speaker 0: it really does.
• 13:21
  Speaker 1: Whether we're talking about Dora Exitability moving off VMware, governing AI agents or tracking AI ROI the ultimate goal for tech leaders right now is taking back control of their architecture and their economics.
• 13:34
  Speaker 0: Taking Back Control I love that but it leaves me with a final maybe slightly terrifying thought for you to ponder.
• 13:41
  Speaker 0: if agentic ai eventually abstracts away all Will our ultimate vendor lock-in simply shift from the cloud provider to the AI agent itself?
• 13:56
  Speaker 1: That is a very scary thought.
• 13:58
  Speaker 0: Right, if you enjoy this episode new episodes drop every two weeks.
• 14:03
  Speaker 0: also check out or other additions on digital products and services defense tech AI in agentic systems green ICT and sustainable AI and health tech.