News for hackers. Stuff that matters.
Re: by rickreynoldssf on Tuesday November 17, 2026 @02:06PM (#50536543)
Apple runs their own cloud.
Re: by lrvick on Tuesday November 17, 2026 @02:11PM (#50536614)
A giant cluster of Puppet managd RedHat computers managed like it is 2007, mixed with Google Cloud.

Apple has literally no idea what they are doing with Linux and cloud.

Re: by Symbiote on Tuesday November 17, 2026 @02:20PM (#50536750)
Up to this point, it seems to have been working well.
Re: by mingus88 on Tuesday November 17, 2026 @02:21PM (#50536752)
They also have private compute cloud, not running Linux

They also use AWS and run servers in China using whatever cloud provider the Party uses

Like you’d expect a trillion dollar global tech enterprise to be, they run a ton of stuff geared toward whatever meets their business objectives

Re: by ibejoeb on Tuesday November 17, 2026 @02:25PM (#50536808)
Interesting. This is the first I've heard of broad service interruption at Apple in a while, as I can't even remember the last time. Do you suspect something about puppet or their overall security posture to be implicated in this?
Re: by rdtsc on Tuesday November 17, 2026 @03:01PM (#50537284)
Hell they were more stable than all the other clouds so far. Maybe a giant cluster of redhat computers managed like 2007 is actually pretty robust compared to super kube control plane v42 with 100 add-ons and layers thrown in on top.
Re: by prmoustache on Tuesday November 17, 2026 @03:03PM (#50537324)
I am not sure what is supposed to be wrong with puppet managed linux servers.
Re: by Nevermark on Tuesday November 17, 2026 @07:25PM (#50540252)
Say “puppet linux servers” really fast several times.

Yeah.

Re: by lrvick on Tuesday November 17, 2026 @08:44PM (#50540832)
Production servers should be hardened, immutable, and remotely attestable appliances. Everyone should be able to prove every line of code in memory at all times, with access to secrets gated on signed quorum approval from multiple reviewers. They should not have dev tools, ssh, a shell, and certainly not capable of blindly modifying themselves at runtime if a single admin of a Puppet control server asks them to. Such tactics mean a single compromised engineer laptop means a compromise of production, and thus a data breach is all but inevitable.

If someone even suggesting Salt, Puppet, or Ansible in a sysadmin interview today for production systems with a straight face I would fail them.

Re: by solyin on Tuesday November 17, 2026 @09:54PM (#50541273)
What's the hardened immutable infra you're using these days?
Re: by edf13 on Wednesday November 18, 2026 @02:16AM (#50542892)
Never worked with a legacy system?
Re: by prmoustache on Wednesday November 18, 2026 @02:47AM (#50543069)
I understand and subscribe to some of the things you say but:

> Such tactics mean a single compromised engineer laptop means a compromise of production, and thus a data breach is all but inevitable.

I hope you don't believe that an immutable image cannot be compromised. The commits done to the build system come from the same engineer laptops and, in a world where CVE are published ao frequently, said compromised image could be deployed largely in only a few minutes hours.

Also there is something to be said with lack of debugging tools. While I agree that reducing the surface of attack is the way to go, I am pretty sure the reason it takes so long for some of the big infra outages we have experienced from various cloud vendors comes from the inability of engineers to log on some systems, observe and potentially fix temporarily by hand to stop a race condition. There is often a race condition and serpent eating its own tail situation involved and logs might not even reach the monitoring infra anymore.

Going back to manage pets is not the way to go but I am not entirely certain removing ability for a subset of engineers to log on systems is exactly the way to go.

Re: by aprdm on Tuesday November 17, 2026 @04:53PM (#50538750)
What's the problem with running puppet in 2026 ?
Re: by electric_mayhem on Tuesday November 17, 2026 @10:18PM (#50541439)
You say that like every group in Apple does things the same way.

They don't.

Re: by swiftcoder on Tuesday November 17, 2026 @02:36PM (#50536972)
> Apple runs their own cloud.

That's not the entirely of their cloud exposure, however. A ton of their stuff runs in AWS, I wouldn't be surprised if they had things on other cloud providers as well.

Re: by mixdup on Tuesday November 17, 2026 @03:05PM (#50537353)
The Microsoft outage wasn't an Azure outage anyway, it was specifically tied to Exchange Online. No one running their own stuff in Azure had any issues during that event
Re: by gr33nq on Tuesday November 17, 2026 @04:01PM (#50538126)
Mostly true, but not entirely. Azure Communication Services (ACS) was down alongside Exchange Online and the other Microsoft 365 applications. I verified this by testing upwards of a dozen times throughout the outage window. There was absolutely no indication made by Microsoft though that ACS was impacted in any way.
Re: by blinding-streak on Tuesday November 17, 2026 @02:53PM (#50537187)
Apple is a massive Google Cloud customer for storage (iCloud) and has been since at least 2018.
Re: by etc-hosts on Tuesday November 17, 2026 @05:39PM (#50539290)
Amazon's internal direction on how they scale out AWS and build new features is heavily guided by "what will it do to one of our biggest customers that has a secret code name but everyone knows its Apple".