Amazon Sable speculation based on CNBC article

Screenshot of a video embed in this article on CNBC
Sable was given a “red” emergency alert in one of the status updates, made a little past 1 p.m., which said it’s “running hot” and “cannot scale.” It also said other services, such as Prime, authentication and video playback, were being “impacted by Sable.”

That’s a portion from this CNBC article. Sable is apparently a technology which helps to scale. In this case it was supposed to properly scale Amazon on Prime Day, but it largely failed.

How can something run hot today? How can something not scale? My theory is that Sable is actually a service that runs within a container within almost every part of AWS. In other words, if I’m Netflix or Medium running on Amazon’s cloud service, called AWS, the actual hardware server is running at least two services, one that is an Amazon virtual server invisible (and secret) to everyone but Amazon, and the other is Netflix’s or Medium’s virtual server.

Something about the wording here makes me think that Sable is a service that has to be used carefully or else it could compromise service for customers other than Amazon. Sable may normally be unnoticeable to the Netflix’s of the world, or at least very hard to notice. But when Sable is reaching its maximum capacity, perhaps it’s creeping into the performance of servers that other companies are relying on. This is totally speculation, but I’m just getting a vibe from the CNBC report that this might be the case.