Latest / Best of LinkedIn: Digital Transformation & Tech / Best of LinkedIn: Cloud Insights CW 03/ 04

Transcript

Best of LinkedIn: Cloud Insights CW 03/ 04 · Best of LinkedIn: Digital Transformation & Tech

• 0:00
  Speaker 1: This episode is provided by Thomas Allgaier and Franis, based on the most relevant LinkedIn posts about cloud in calendar weeks O three and O four.
• 0:08
  Speaker 1: Franis enables enterprises with market technology and competitive intelligence for portfolio and strategy development.
• 0:14
  Speaker 1: Welcome
• 0:15
  Speaker 0: back to our deep dive.
• 0:16
  Speaker 0: It's great to have you with us.
• 0:18
  Speaker 0: You know, if you were watching the LinkedIn feeds in mid January, twenty twenty six, you probably felt a real shift in the conversation.
• 0:25
  Speaker 0: Oh,
• 0:25
  Speaker 1: definitely the whole cloud topic.
• 0:26
  Speaker 1: Yeah.
• 0:27
  Speaker 1: It isn't just about speed or new features anymore.
• 0:29
  Speaker 1: It's gotten very serious.
• 0:30
  Speaker 1: Very fast.
• 0:31
  Speaker 0: It has.
• 0:32
  Speaker 0: It feels like the industry came back from the holiday break, looked at everything and just said, okay, party's over.
• 0:37
  Speaker 0: Time
• 0:37
  Speaker 1: to grow up.
• 0:38
  Speaker 1: Yeah.
• 0:38
  Speaker 1: Exactly.
• 0:39
  Speaker 1: We're seeing this massive focus on boundaries.
• 0:41
  Speaker 1: You know, where does my data actually live?
• 0:43
  Speaker 1: How do we stop hemorrhaging money?
• 0:45
  Speaker 1: And maybe how do we stop getting hacked by really simple mistakes?
• 0:49
  Speaker 0: That's the perfect way to put it.
• 0:51
  Speaker 0: So we've sifted through all the noise and really distilled it down to three huge pillars that define these last couple of weeks.
• 0:58
  Speaker 0: First step, we're going to talk about sovereignty and Right.
• 1:01
  Speaker 1: AWS made a huge move there.
• 1:02
  Speaker 0: A huge move?
• 1:04
  Speaker 0: But the legal pushback is, I think, even more interesting.
• 1:07
  Speaker 1: Then we're going to do a serious reality check on cost optimization and fine ops and a little spoiler here.
• 1:15
  Speaker 1: If you think your dashboard is saving you money, you're probably wrong.
• 1:20
  Speaker 0: We'll also get into how AI is just completely breaking the old billing models.
• 1:24
  Speaker 1: And finally, we'll tackle security and secops.
• 1:27
  Speaker 1: There's a really loud message from the senior engineering community, and it's basically, stop buying cools.
• 1:33
  Speaker 0: Start understanding how a breach actually works.
• 1:36
  Speaker 1: Okay, so let's dive right in.
• 1:37
  Speaker 1: Pillar one.
• 1:38
  Speaker 1: Sovereignty.
• 1:39
  Speaker 1: you can't miss the headline.
• 1:40
  Speaker 1: the AWS European sovereign cloud is officially live.
• 1:44
  Speaker 0: it is and we need to pause here because Sovereign cloud is a term that gets thrown around a lot.
• 1:48
  Speaker 1: a lot of marketing fluff usually
• 1:50
  Speaker 0: right, but according to posts from make wheeze Miller and Mateo de Pascal This launch is a genuine game changer.
• 1:56
  Speaker 0: It's not just a new label on an old service.
• 1:59
  Speaker 1: Okay, so they're emphasizing that the first region is physically in Brandenburg, Germany, but Let's be honest, AWS has had data centers in Frankfurt for years.
• 2:09
  Speaker 1: So for anyone listening who's thinking, so what?
• 2:14
  Speaker 1: Why is this different?
• 2:15
  Speaker 0: That is the crucial question.
• 2:17
  Speaker 0: And the difference is all in the architecture.
• 2:19
  Speaker 0: Matera de Pascal pointed out that this cloud is physically and logically separate.
• 2:23
  Speaker 0: In, you know, cloud terms, we call that a separate partition.
• 2:26
  Speaker 0: A
• 2:26
  Speaker 1: partition.
• 2:27
  Speaker 1: Okay, break that down for us.
• 2:28
  Speaker 1: What does that mean for a business actually running something on it?
• 2:31
  Speaker 0: OK, so think of the standard AWS global network as one giant house.
• 2:36
  Speaker 0: You have different rooms, US East, Frankfurt, Tokyo, and they're separate rooms, but they share the same plumbing, the same wiring.
• 2:42
  Speaker 1: And the same landlord has the keys to all the doors.
• 2:45
  Speaker 0: Exactly.
• 2:45
  Speaker 0: This new sovereign cloud is a completely separate building.
• 2:48
  Speaker 0: Down the street, different keys, different plumbing.
• 2:50
  Speaker 0: So
• 2:50
  Speaker 1: it creates a hard break.
• 2:51
  Speaker 0: A very hard break.
• 2:52
  Speaker 0: It has its own billing systems.
• 2:54
  Speaker 0: It has its own identity and access management, its own IAM system.
• 2:59
  Speaker 0: I mean, that's huge.
• 3:00
  Speaker 1: So an identity.
• 3:01
  Speaker 1: in the global AWS cloud doesn't even exist here.
• 3:03
  Speaker 0: It doesn't.
• 3:04
  Speaker 0: And the metadata, which is often the really sticky point with privacy laws, all of it stays in the EU.
• 3:10
  Speaker 0: And crucially, the operators, the actual people with keys to the servers are all EU residents.
• 3:18
  Speaker 1: That is a massive shift.
• 3:19
  Speaker 1: We're so used to that.
• 3:21
  Speaker 1: follow the Sun support model, where an engineer in Seattle might be patching a server in Dublin.
• 3:25
  Speaker 1: That's
• 3:26
  Speaker 0: gone here.
• 3:27
  Speaker 0: And it seems like it's just the start.
• 3:28
  Speaker 0: We saw updates from Susanna Curic and Ivo Pinto highlighting expansion plans.
• 3:33
  Speaker 1: Yeah, they're already talking about local zones in Belgium, the Netherlands, and Portugal.
• 3:37
  Speaker 0: So the physical footprint is expanding fast, trying to bring that latency down while keeping data inside those borders.
• 3:44
  Speaker 1: So on paper... This sounds perfect for the public sector, healthcare, finance, basically anyone terrified of GDPR.
• 3:52
  Speaker 1: But, and there's always a but.
• 3:54
  Speaker 1: There
• 3:54
  Speaker 0: is always a but.
• 3:55
  Speaker 1: Not everyone is buying
• 3:56
  Speaker 0: it.
• 3:56
  Speaker 0: No, not at all.
• 3:57
  Speaker 0: In fact, there's a very vocal counter narrative bubbling up that's calling this an illusion of sovereignty.
• 4:02
  Speaker 1: Sovereignty washing was the phrase I kept seeing.
• 4:04
  Speaker 0: That's the one.
• 4:05
  Speaker 0: Julius Knuff and Fred C. Veltuz were particularly blunt about it.
• 4:09
  Speaker 0: Their whole argument just cuts right through the technical stuff we just talked about and hits a legal brick wall.
• 4:14
  Speaker 0: This
• 4:14
  Speaker 1: is the U.S.
• 4:15
  Speaker 1: Cloud Act issue, isn't it?
• 4:16
  Speaker 0: It is.
• 4:17
  Speaker 0: And this is where the tech hits the real world.
• 4:20
  Speaker 0: The argument from critics like Julius Knuff is pretty simple.
• 4:23
  Speaker 0: It doesn't matter if the server is in Brandenburg.
• 4:26
  Speaker 0: It doesn't matter if the admin is German.
• 4:28
  Speaker 1: If the parent company is American.
• 4:30
  Speaker 0: If the parent company Amazon is based in the
• 4:32
  Speaker 0: U.S.,
• 4:33
  Speaker 0: they fall under U.S.
• 4:34
  Speaker 0: law.
• 4:35
  Speaker 0: And theoretically, a U.S.
• 4:37
  Speaker 0: court could compel that parent company to hand over data, no matter where it sits.
• 4:41
  Speaker 1: Yassi Romanetz had a fantastic breakdown of this.
• 4:44
  Speaker 1: She framed it around the legal concept of foreign interference and possession, custody, or control.
• 4:51
  Speaker 0: That analysis was brilliant.
• 4:52
  Speaker 0: She argued the legal test is whether the US entity actually has control.
• 4:56
  Speaker 0: And AWS's strategy here is, well, it's very clever.
• 4:59
  Speaker 0: How so?
• 5:00
  Speaker 0: By creating this technical partition, by removing the admin pads that would let a US engineer log in, they're trying to build a case that they technically cannot comply with a US warrant.
• 5:11
  Speaker 1: Oh, I see.
• 5:11
  Speaker 1: So they can go to a US judge and say, Your Honor, we'd love to help, but we literally cannot access that data.
• 5:16
  Speaker 1: The drawbridge is up.
• 5:17
  Speaker 0: Precisely.
• 5:18
  Speaker 0: It's a can't not won't defense.
• 5:20
  Speaker 0: But for purists like Fred C. Velduis, that's still way too risky.
• 5:25
  Speaker 0: They argue as long as the corporate org chart leads back to Washington, the risk is still there.
• 5:30
  Speaker 1: And this skepticism is just opening the door wide for competitors.
• 5:34
  Speaker 1: I saw a post from Jaco Landlust at Oracle that was, well, that's called spicy.
• 5:39
  Speaker 0: It was a bit of friendly fire, yes.
• 5:41
  Speaker 0: You basically just welcomed AWS to the club, pointing out that Oracle has been running a sovereign cloud model for two years.
• 5:47
  Speaker 0: No,
• 5:47
  Speaker 1: AWS is actually playing catch-up in this niche.
• 5:50
  Speaker 0: In this specific niche, yeah.
• 5:52
  Speaker 0: And it's not just the American Giants fighting.
• 5:54
  Speaker 0: Weiland Holfelder noted a huge milestone for S-three NS.
• 5:58
  Speaker 1: S-three NS.
• 5:59
  Speaker 1: For anyone not up on French tech partnerships, what is that?
• 6:02
  Speaker 0: So S-three-N-S is a partnership between Google Cloud and Thales, the French defense and security company, and they just achieved Secdom Cloud's three point two qualification.
• 6:11
  Speaker 1: Secdom Cloud.
• 6:12
  Speaker 1: It sounds like a droid from Star Wars.
• 6:14
  Speaker 0: It does, doesn't it?
• 6:15
  Speaker 0: But in the regulatory world, it is absolute gold.
• 6:19
  Speaker 0: It is the highest security standard for trusted cloud providers in France.
• 6:24
  Speaker 0: It's incredibly hard to get.
• 6:25
  Speaker 1: So you have the US giants building these partitions, but then you have the true European alternatives.
• 6:32
  Speaker 1: Bern Wagner or Bernie highlighted a partnership I thought was really telling.
• 6:36
  Speaker 1: Send a clinic in and stack it.
• 6:37
  Speaker 0: This is such a crucial example.
• 6:39
  Speaker 0: Stacket is the cloud arm of the Schwartz Group.
• 6:41
  Speaker 1: The owners of Lidl and Coffland.
• 6:43
  Speaker 1: Right.
• 6:43
  Speaker 0: A massive European retail giant turning into a tech provider.
• 6:47
  Speaker 0: And Santa Clinic is a major hospital chain.
• 6:50
  Speaker 1: So you have a German healthcare provider choosing a cloud provider with absolutely no U.S.
• 6:55
  Speaker 1: parent company.
• 6:56
  Speaker 1: Zero.
• 6:56
  Speaker 0: And for an organization dealing with patient data, that just removes the entire US Cloud Act headache from the equation.
• 7:03
  Speaker 1: So the spectrum is really clear now.
• 7:04
  Speaker 1: You've got Standard Cloud on one end.
• 7:06
  Speaker 1: In the middle, you have US Cloud with European partitions like AWS and Google Sales.
• 7:11
  Speaker 1: And then on the far end, native European Cloud like Stack-It.
• 7:15
  Speaker 0: Exactly.
• 7:16
  Speaker 0: And twenty twenty six is going to be the year where companies have to pick a side.
• 7:19
  Speaker 0: It's not a vague cloud first strategy anymore.
• 7:22
  Speaker 0: It's a which jurisdiction first strategy.
• 7:25
  Speaker 1: Fascinating.
• 7:26
  Speaker 1: Okay, let's pivot.
• 7:27
  Speaker 1: Pillar two.
• 7:28
  Speaker 1: We know where the data lives.
• 7:30
  Speaker 1: Now let's talk about why it's bankrupting us.
• 7:32
  Speaker 1: Finops.
• 7:33
  Speaker 0: Ah, yes.
• 7:34
  Speaker 0: The art of not going broke in the cloud.
• 7:37
  Speaker 1: You know, I read a post by Isaiah Michael that really hit home.
• 7:40
  Speaker 1: He basically said, stop blaming the technology for your bill.
• 7:43
  Speaker 0: That was some harsh.
• 7:45
  Speaker 0: but necessary truth.
• 7:46
  Speaker 0: He framed a cost overruns as an ownership problem, not
• 7:50
  Speaker 1: a tech problem.
• 7:51
  Speaker 1: Can you unpack that a little?
• 7:52
  Speaker 1: Because I think every engineer listening has probably spun up an EC-II instance and forgotten about it.
• 7:57
  Speaker 0: That is exactly it.
• 7:58
  Speaker 0: Isaiah listed all the classics, EC-II instances running just in case, massive RDS databases sitting idle because no one wants to be the one to delete them, snapshots that are five years old.
• 8:08
  Speaker 1: Right.
• 8:09
  Speaker 0: His point is, the cloud is doing exactly what you told it to.
• 8:12
  Speaker 0: It's running the servers.
• 8:13
  Speaker 0: The fact that you're not using them is a human process glitch, not a software glitch?
• 8:17
  Speaker 1: It's like a gym membership.
• 8:18
  Speaker 1: You can't blame the gym for charging you if you never show up.
• 8:22
  Speaker 1: You signed the contract.
• 8:23
  Speaker 0: It's the perfect analogy, and this ties directly into a really insightful point by Mohamed C. or Moe about dockboards.
• 8:30
  Speaker 0: He calls it the dashboard fallacy.
• 8:32
  Speaker 1: We do love our dashboards.
• 8:33
  Speaker 1: Green is good, red is panic.
• 8:35
  Speaker 0: But Moe are used, most of them are useless.
• 8:38
  Speaker 0: They answer the wrong question.
• 8:39
  Speaker 0: They answer a finance question, which is how much did we spend?
• 8:42
  Speaker 1: Instead of the engineering question, what changed and why?
• 8:45
  Speaker 0: That's the critical distinction.
• 8:47
  Speaker 0: As a developer, knowing the bill went up five thousand dollars doesn't help me fix anything.
• 8:52
  Speaker 0: Engineers need signals, not receipts.
• 8:55
  Speaker 0: They need a dashboard that says, hey, that microservice you deployed yesterday, your data transfer costs just spike four hundred percent.
• 9:01
  Speaker 0: That connects cause and effect.
• 9:02
  Speaker 1: So we need better signals.
• 9:04
  Speaker 1: But to get those, we all need to speak the same language.
• 9:07
  Speaker 1: Ruben van der Stokt was pushing very hard for something called focuses.
• 9:11
  Speaker 0: Yes, focuses.
• 9:13
  Speaker 0: Finops, open cost and usage specification.
• 9:15
  Speaker 1: That's a mouthful.
• 9:17
  Speaker 1: Why should we care about another acronym?
• 9:18
  Speaker 0: Because right now, the billing data from AWS looks totally different from Azure, which looks different from Google Cloud.
• 9:25
  Speaker 0: If you're a multi-cloud company, trying to merge those bills is a complete nightmare.
• 9:30
  Speaker 0: Focus is just an attempt to standardize it.
• 9:32
  Speaker 1: So it's like agreeing that a meter is a meter, no matter whose ruler you're using.
• 9:37
  Speaker 0: Exactly.
• 9:38
  Speaker 0: But just as we're getting our heads around that, twenty twenty six throws us this huge curveball,
• 9:43
  Speaker 1: AI
• 9:44
  Speaker 0: fine ops.
• 9:45
  Speaker 1: This is the new frontier.
• 9:47
  Speaker 1: Nicholas Sondrini wrote a deep piece on this, and it's a real mind-bender.
• 9:51
  Speaker 1: The old Finops model is all about, you know, provisioned infrastructure.
• 9:54
  Speaker 1: I bought a server.
• 9:55
  Speaker 1: What does it cost per hour?
• 9:56
  Speaker 0: But with generative AI, the cost driver changes completely.
• 10:00
  Speaker 0: It's not about the server anymore.
• 10:01
  Speaker 1: It's just to the inference level, right?
• 10:03
  Speaker 0: Correct.
• 10:03
  Speaker 0: It becomes about decision costs.
• 10:05
  Speaker 0: Every single time the AI answers a query, that costs money, but not all queries are equal.
• 10:10
  Speaker 1: Right.
• 10:11
  Speaker 1: If I have to write a haiku, that's cheap.
• 10:12
  Speaker 1: If I ask it to analyze a fifty-page legal contract, That's expensive.
• 10:16
  Speaker 0: Exactly.
• 10:17
  Speaker 0: And Nicholas suggests we need totally new metric.
• 10:19
  Speaker 0: Things like cost per answer and my favorite accuracy adjusted cost.
• 10:23
  Speaker 1: Accuracy adjusted cost.
• 10:25
  Speaker 1: I love that.
• 10:26
  Speaker 1: Because if you use a cheap small model, but it gives you the wrong answer three times and you have to re-prompt it.
• 10:31
  Speaker 0: Then your so-called cheap model just became more expensive than the premium one that would have gotten it right the first time.
• 10:37
  Speaker 0: Mirko Taktimon from OneAI also chimed in here, calling out the black box.
• 10:43
  Speaker 0: of API calls.
• 10:44
  Speaker 1: It really is a black box.
• 10:45
  Speaker 1: You send a prompt into the void, you get an answer, and then later you get a bill.
• 10:48
  Speaker 1: You don't know the token count until it's too late.
• 10:51
  Speaker 1: And
• 10:51
  Speaker 0: for a business trying to budget, that is a nightmare.
• 10:53
  Speaker 0: Mirko is arguing for transparent pricing so businesses can actually calculate the ROI of an AI feature before they build it.
• 11:01
  Speaker 1: Wow.
• 11:01
  Speaker 1: So the days of just build it and see are over.
• 11:04
  Speaker 1: We're moving into an era of like unit economics for thoughts.
• 11:08
  Speaker 1: Unit
• 11:08
  Speaker 0: economics for thoughts.
• 11:09
  Speaker 0: I like that.
• 11:10
  Speaker 0: That's exactly what it is.
• 11:11
  Speaker 0: Okay.
• 11:12
  Speaker 1: On to our third and final pillar.
• 11:15
  Speaker 1: We've locked down the data, we're counting the panties.
• 11:18
  Speaker 1: Now how do we stop the bad guys from burning it all down?
• 11:20
  Speaker 1: Security.
• 11:21
  Speaker 1: SecOps.
• 11:21
  Speaker 1: There
• 11:21
  Speaker 0: was a piece of advice from Taymor Ejalal that I think every junior cloud engineer and frankly a lot of senior ones really needs to hear.
• 11:29
  Speaker 1: I know the one.
• 11:30
  Speaker 1: Stop learning more AWS services.
• 11:33
  Speaker 0: It sounds so counterintuitive for a career in cloud, doesn't it?
• 11:36
  Speaker 0: Stop learning cloud.
• 11:37
  Speaker 0: But his point is profound.
• 11:38
  Speaker 0: He argues that engineers are too focused on collecting badges.
• 11:42
  Speaker 1: I know fifty AWS services.
• 11:44
  Speaker 0: Right.
• 11:45
  Speaker 0: And not focused enough on understanding how breaches actually happen.
• 11:48
  Speaker 0: He listed the classics, didn't he?
• 11:50
  Speaker 1: Leaked credentials in a public GitHub repo, overly permissive IAM roles exposed S three buckets.
• 11:57
  Speaker 0: Exactly.
• 11:57
  Speaker 0: It is almost never some mission impossible zero day exploit.
• 12:01
  Speaker 0: It's almost always someone leaving the keys in the front door.
• 12:04
  Speaker 0: Tamer's point is.
• 12:05
  Speaker 0: master the fundamentals, identity, networking, encryption.
• 12:09
  Speaker 0: If you get those, the specific service doesn't
• 12:11
  Speaker 1: matter.
• 12:12
  Speaker 1: It's about the mechanics of the breach.
• 12:13
  Speaker 1: But the industry just keeps trying to solve this by buying more tools.
• 12:17
  Speaker 1: Constantino's Evangelacos, he goes by Gus, had this really sharp critique of the whole runtime security market.
• 12:23
  Speaker 1: Oh, the
• 12:23
  Speaker 0: agents break things discussion.
• 12:24
  Speaker 0: If you have ever worked in operations, you felt this in your soul.
• 12:27
  Speaker 1: Give us the context.
• 12:28
  Speaker 1: What's runtime security?
• 12:30
  Speaker 0: So traditionally to secure a server, you install software on it, an agent.
• 12:35
  Speaker 0: And this agent watches everything the server does and stops bad things.
• 12:39
  Speaker 0: Sounds great, right?
• 12:40
  Speaker 0: In
• 12:40
  Speaker 1: theory, yes.
• 12:41
  Speaker 0: But in practice, Gus paints a picture we all recognize.
• 12:44
  Speaker 0: A company buys a fancy runtime tool.
• 12:47
  Speaker 0: Three years later, they've deployed it to maybe ten percent of their servers.
• 12:52
  Speaker 1: Because the developers are an open revolt.
• 12:53
  Speaker 0: Exactly.
• 12:54
  Speaker 0: The developers are saying, that agent uses twenty percent of my CPU, or it crashed my build, or it caused a kernel panic and prod.
• 13:02
  Speaker 0: So they just block the rollout.
• 13:04
  Speaker 0: The company thinks it's secure, but the tool is sitting on a shelf.
• 13:07
  Speaker 1: So what's the alternative?
• 13:08
  Speaker 1: If agents are the problem, what do we do?
• 13:11
  Speaker 0: Gus advocates for agentless scanning.
• 13:14
  Speaker 0: This is what companies like Orca Security popularized.
• 13:17
  Speaker 0: Instead of installing software inside the server, you take a snapshot of the server's disk from the outside, at the cloud provider level, and you scan that.
• 13:25
  Speaker 1: Ah, so it's non-intrusive.
• 13:26
  Speaker 1: The application has no idea it's even being scanned.
• 13:28
  Speaker 0: No performance hit, no crashes.
• 13:31
  Speaker 0: Gus points out this means you get one hundred percent visibility during a proof of concept.
• 13:36
  Speaker 0: You don't wait a year for a rollout.
• 13:38
  Speaker 0: You see all the problems on day one.
• 13:40
  Speaker 1: That speed to value is critical.
• 13:42
  Speaker 1: But even that feels reactive.
• 13:44
  Speaker 1: Lefteris Karagorju brought this back to the absolute fundamentals.
• 13:48
  Speaker 0: Yes, the napkin phase.
• 13:50
  Speaker 0: His whole thing is, create architectural diagrams before you build anything.
• 13:54
  Speaker 1: It seems so obvious.
• 13:55
  Speaker 1: But be honest, how many times do people just start coding terraform without ever drawing the box first?
• 14:00
  Speaker 0: All the time.
• 14:01
  Speaker 0: And Lefteris' quote is one for the wall.
• 14:04
  Speaker 0: You cannot secure a request flow.
• 14:05
  Speaker 0: you don't understand.
• 14:07
  Speaker 0: If you can't trace the data path, you don't know where your attack surface is, you're just guessing.
• 14:11
  Speaker 0: And
• 14:11
  Speaker 1: finally, Rami Akifaji rounded this out by listing the core AWS principles.
• 14:16
  Speaker 1: Automation, visibility, and auditability.
• 14:19
  Speaker 0: The automation part is key.
• 14:20
  Speaker 0: If you're clicking around in the console to secure things, you have already lost.
• 14:24
  Speaker 0: Humans make mistakes.
• 14:25
  Speaker 0: Security has to be code.
• 14:26
  Speaker 0: It has to be reproducible.
• 14:28
  Speaker 0: So
• 14:28
  Speaker 1: pulling this all together.
• 14:29
  Speaker 1: We had these three massive themes colliding in January, twenty twenty six.
• 14:33
  Speaker 1: Sovereignty, phenops, sick ops.
• 14:35
  Speaker 0: And if you connect the dots, it's really a story about maturity.
• 14:39
  Speaker 1: Also,
• 14:40
  Speaker 0: look at sovereignty.
• 14:41
  Speaker 0: We're moving from vague promises to hard legal and technical partitions.
• 14:46
  Speaker 0: We're maturing from trust us to verify
• 14:49
  Speaker 1: us and in phenops.
• 14:51
  Speaker 0: We're moving from the immature question of how much did we spend to the mature question of what is the business value of this specific AI decision.
• 14:58
  Speaker 1: And in security, it's moving from collecting tools to understanding architecture.
• 15:02
  Speaker 0: Exactly.
• 15:03
  Speaker 0: Sovereignty provides the legal framework.
• 15:05
  Speaker 0: Finops provides the economic discipline.
• 15:08
  Speaker 0: And sickups provides the operational integrity.
• 15:10
  Speaker 0: You can't excel at cloud in twenty twenty six without doing all three at once.
• 15:15
  Speaker 1: It's not enough to just be in the cloud anymore.
• 15:16
  Speaker 1: You have to be sovereign, solvent and secure.
• 15:19
  Speaker 1: That's
• 15:19
  Speaker 0: the trifecta.
• 15:20
  Speaker 1: Before we wrap, I want to leave our listeners with one last thought.
• 15:23
  Speaker 1: We talked about the decision cost of AI.
• 15:26
  Speaker 1: We talked about these sovereign clouds in Europe.
• 15:28
  Speaker 1: As those trends converge, I wonder, are we going to start seeing a sovereignty premium on AI?
• 15:35
  Speaker 1: That's
• 15:35
  Speaker 0: a really interesting angle.
• 15:36
  Speaker 1: Think about it.
• 15:37
  Speaker 1: Will a decision made by an AI hosted in that secure Brandenburg cloud cost more than one from a massive shared farm in Virginia?
• 15:47
  Speaker 1: And if it does, is that a price?
• 15:49
  Speaker 1: businesses will pay for privacy?
• 15:51
  Speaker 0: That raises a fundamental question about the economics of privacy.
• 15:54
  Speaker 0: Is privacy a luxury good?
• 15:55
  Speaker 0: I suspect the market will answer that question very soon, and the answer might be expensive.
• 16:00
  Speaker 1: Indeed.
• 16:01
  Speaker 1: Well, that brings us to the end of this deep dive.
• 16:04
  Speaker 1: If you enjoyed this episode, new episodes drop every two weeks.
• 16:08
  Speaker 1: Also check out our other editions on ICT and tech, digital products and services, artificial intelligence, sustainability, and green ICT, defense tech, and health.
• 16:17
  Speaker 0: Thank you so much for listening.
• 16:18
  Speaker 0: There's always more to learn, so keep questioning and keep exploring.
• 16:21
  Speaker 0: Don't
• 16:22
  Speaker 1: forget to subscribe.
• 16:22
  Speaker 1: We'll catch you in the next one.